This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/16919] recvmsg standard compliance


https://sourceware.org/bugzilla/show_bug.cgi?id=16919

--- Comment #8 from Rich Felker <bugdal at aerifal dot cx> ---
I don't think fixing the kernel to ignore the upper 32 bits of these
wrongly-64-bit fields would "break userspace". It would mask bugs in old
applications that wrote huge (>0xffffffff) values to the fields and expected to
get an error from doing so rather than for the high bits to be ignored, but I
really doubt any such applications exist. For all applications using the
interfaces correctly, old apps with the wrong struct definition would already
be storing zeros in the high bits, and new applications with the right struct
definition would be leaving junk in the upper bits for the kernel (or, for the
time being, glibc when it does the fixup in userspace to support old kernels)
to ignore.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]