From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: libc.so symbols that are not reserved
Date: Mon, 11 Nov 2013 23:41:29 -0500 [thread overview]
Message-ID: <20131112044128.GO24286@brightrain.aerifal.cx> (raw)
In-Reply-To: <20131112040736.GQ1685@port70.net>
On Tue, Nov 12, 2013 at 05:07:36AM +0100, Szabolcs Nagy wrote:
> > What would in principle be problematic is if standard C or POSIX
> > functions in libc depended on any of these symbols, since an
> > application could interpose unrelated functionality with the same
> > name. In practice that doesn't matter for dynamic linking since
> > -Bsymbolic is used, but it would matter for static linking of course.
> > As far as I know musl has no such issues (except for treating dup3,
> > pipe2, etc. as if they were in POSIX since they will be in the next
> > issue; if you object to that I'm not opposed to adding __-prefixed
> > versions).
>
> actually dup3 is __ prefixed already
Interesting...wonder why I did that one but not pipe2...?
> so the only exceptions are
>
> pipe2
Known.
> stdin
> stdout
> stderr
Pending interpretation from WG14. :-)
> getservbyname_r
> getservbyport_r
Indeed. I must have been mistakenly thinking getservbyname and
getservbyport were obsolete already, but they're not even marked
obsolescent, despite getaddrinfo and getnameinfo offering replacement
functionality that's actually thread-safe and clean. The failure to
shade these functions [OB] perhaps should be reported as a bug against
POSIX.
> if pipe2 and dup3 are in the next standard then i dont think
> they have to be weak
Yeah, I'm fairly indifferent on it too, but I'll change them if anyone
complains.
Rich
prev parent reply other threads:[~2013-11-12 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 1:39 Szabolcs Nagy
2013-11-12 2:55 ` Rich Felker
2013-11-12 4:07 ` Szabolcs Nagy
2013-11-12 4:41 ` Rich Felker [this message]
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=20131112044128.GO24286@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).