From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: __xmknod, __sysv_signal
Date: Fri, 18 Apr 2014 22:52:04 -0400 [thread overview]
Message-ID: <20140419025204.GS26358@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAL3m8eBHheDR-rFHfuSXyJ7qUyjUCYw09oOfoMzAkYrxFiUU6g@mail.gmail.com>
On Fri, Apr 18, 2014 at 09:18:33PM -0500, M Farkas-Dyck wrote:
> A dynamic-linked binary blob I have wants these. Are these appropriate
> to include in musl? I have a patch ready.
Send the patch and I'll review it.
For __xmknod, I think this is just the ABI symbol glibc uses for
mknod, and we could certainly add it (though I question whether there
are any useful programs using it that couldn't just be rebuilt against
musl).
For __sysv_signal, I'm not sure what we should do. Its semantics are
different from signal(), but it's doubtful that any program actually
intended to request the sysv semantics (they're fundamentally broken
and have race conditions that renders any program using them buggy) so
it might just make more sense to have it be an alias for signal than
to actually implement the broken sysv behavior. (Most likely is that
glibc's weird behavior with certain feature test macros caused a
program to inadvertently pull in the broken sysv version of signal
rather than the default one.)
Rich
next prev parent reply other threads:[~2014-04-19 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 2:18 M Farkas-Dyck
2014-04-19 2:52 ` Rich Felker [this message]
2014-04-19 3:11 ` M Farkas-Dyck
2014-05-01 0:32 ` Rich Felker
2014-05-06 16:55 ` M Farkas-Dyck
2014-05-07 3:17 ` Rich Felker
2014-05-07 10:18 ` Rob Landley
2014-05-07 22:58 ` Rich Felker
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=20140419025204.GS26358@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).