public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pterjan at mandriva dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11099] New: INT_FIELD_MAYBE_NULL changed behaviour on x86_64
Date: Wed, 16 Dec 2009 18:41:00 -0000	[thread overview]
Message-ID: <20091216184119.11099.pterjan@mandriva.com> (raw)

We had password aging bugs on Mandriva and I found that when a field of
/etc/shadow contains -1, it gets 32 bits value of -1 on x86_64 even if the field
is long in the struct.

According to the doc it should indeed be empty to disable instead of containing
-1, but well the field is signed and nothing prevents from having a negative value

It used to work and the behavior change broke tests like spw->sp_* != -1 in pam
modules

The change was introduced by
http://repo.or.cz/w/glibc.git/commitdiff/1e545d0185072ac0d4646223d509c3692cbe550a with
a commit message unrelated to this part of the commit

-- 
           Summary: INT_FIELD_MAYBE_NULL changed behaviour on x86_64
           Product: glibc
           Version: 2.11
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: pterjan at mandriva dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=11099

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2009-12-16 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 18:41 pterjan at mandriva dot com [this message]
2009-12-17  9:21 ` [Bug libc/11099] " schwab at linux-m68k dot org
2010-04-05  4:33 ` drepper at redhat dot com
2010-04-05 15:14 ` pterjan at mandriva dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091216184119.11099.pterjan@mandriva.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).