This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/11099] New: INT_FIELD_MAYBE_NULL changed behaviour on x86_64
- From: "pterjan at mandriva dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 16 Dec 2009 18:41:19 -0000
- Subject: [Bug libc/11099] New: INT_FIELD_MAYBE_NULL changed behaviour on x86_64
- Reply-to: sourceware-bugzilla at sourceware dot org
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.