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 network/12926] getaddrinfo()/make_request() may spin forever


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

--- Comment #12 from James E. King, III <jim.king at simplivity dot com> ---
The issue I originally experienced was causes by defect 15946, however I still
believe that since the interface documentation for "recvmsg" clearly states
that 0 is a valid return for a disconnection then the glibc code must honor
that even if the kernel is not expected to use it.  The kernel might change
because the interface documentation says that it can, and a future kernel
change might then break things in glibc, where glibc would enter an infinite
loop.  So even if we never expect 0 to come back from recvmsg on the NETLINK
socket, we still need to code for it because it is a valid response.

-- 
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]