[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140527112954.GL12324@port70.net>
Date: Tue, 27 May 2014 13:29:54 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: [UGLY PATCH v3] Support for no-legacy-syscalls archs
* Rich Felker <dalias@...c.org> [2014-05-27 01:26:25 -0400]:
> In the case of epoll, etc. I reworked the code to always prefer the
> new syscalls and only fallback to the old ones if (1) they exist, and
> (2) the new one returned ENOSYS. signalfd already has fallback code
> that handles FD_CLOEXEC as best it can when the new syscall is not
> available, but the others seem to be lacking the proper fallback code
> so I should perhaps add that too.
SOCK_CLOEXEC and SOCK_NONBLOCK fallbacks for socketpair are missing too
> +#ifdef SYS_pausex
> + __syscall(SYS_pause);
> +#else
> + __syscall(SYS_futex, &lock, FUTEX_WAIT, 1, 0);
> +#endif
pausex typo
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
