This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Fix resolver bind, getsockname namespace (bug 17733)
- From: Joseph Myers <joseph at codesourcery dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 22 Dec 2014 12:52:18 +0000
- Subject: Re: Fix resolver bind, getsockname namespace (bug 17733)
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1412191854520 dot 3401 at digraph dot polyomino dot org dot uk> <CAMe9rOqqhnTfKevkyNHBoQ1miW2MAXz1fkwuqGE3DtbvWisXgA at mail dot gmail dot com>
On Sun, 21 Dec 2014, H.J. Lu wrote:
> Do sysdeps/unix/sysv/linux/listen.S and sysdeps/unix/sysv/linux/setsockopt.S
> have the same issue? Does the linknamespace test check them?
I don't see any linknamespace test failures (even XFAILed) mentioning
those functions. That is, there seem to be no cases (for the standards
currently tested, at least) of a function in a standard lacking those
functions calling listen / setsockopt, or calling __listen / __setsockopt
and thereby bringing in strong symbols for listen / setsockopt.
Thus, while I think a corresponding change to those files would make sense
as a cleanup, it would not fix a user-visible bug (and so would not need a
bug filed in Bugzilla).
--
Joseph S. Myers
joseph@codesourcery.com