From: Alexander Larsson <alexander.larsson@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: musl@lists.openwall.com
Subject: Re: Using direct socket syscalls on x86_32 where available?
Date: Tue, 28 Jul 2015 09:44:26 +0200 [thread overview]
Message-ID: <CAHr-LrakCdR5+kRg=tA67VZk4ndaC_VJjCa_PUeBcDgmMzrsOw@mail.gmail.com> (raw)
In-Reply-To: <55B6C543.1020108@amacapital.net>
On Tue, Jul 28, 2015 at 1:56 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>
> One way to implement it would be to favor the new syscalls but to set some
> variable the first time one of them returns ENOSYS. Once that happens,
> either all of them could fall back to socketcall or just that one syscall
> could.
>
> Or you could just avoid implementing it and see if anyone complains. It's
> plausible that xdg-app might start requiring the new syscalls (although it
> would presumably not kill you if tried to use socketcall).
>
> Alex, if glibc started using the new syscalls, would you want to require
> them inside xdg-app?
Probably not. At this point 32bit x86 just is not interesting enough
for such extra pain. We'll just not filter on address types on 32bit.
next prev parent reply other threads:[~2015-07-28 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 17:54 Andy Lutomirski
2015-07-25 18:35 ` Szabolcs Nagy
2015-07-26 16:33 ` Justin Cormack
2015-07-26 16:59 ` Rich Felker
2015-07-27 23:56 ` Andy Lutomirski
2015-07-28 0:45 ` Rich Felker
2015-07-28 1:04 ` Andy Lutomirski
2015-07-28 1:21 ` Rich Felker
2015-07-28 1:38 ` Andy Lutomirski
2015-07-28 12:05 ` Szabolcs Nagy
2015-07-28 7:44 ` Alexander Larsson [this message]
2015-07-29 12:51 ` Justin Cormack
2015-07-29 18:32 ` Andy Lutomirski
2015-07-29 23:14 ` Justin Cormack
2015-07-31 23:13 ` Brad Conroy
2015-08-01 0:02 ` Rich Felker
2015-08-01 3:32 ` Brad Conroy
2015-08-01 3:47 ` Rich Felker
2015-08-01 11:24 ` u-wsnj
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='CAHr-LrakCdR5+kRg=tA67VZk4ndaC_VJjCa_PUeBcDgmMzrsOw@mail.gmail.com' \
--to=alexander.larsson@gmail.com \
--cc=luto@amacapital.net \
--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).