[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrX_b68Ex+i4Aq=Nep-ADvSD=VDmj-K8XEaUB+4JNba2Tw@mail.gmail.com>
Date: Sat, 25 Jul 2015 10:54:28 -0700
From: Andy Lutomirski <luto@...capital.net>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Using direct socket syscalls on x86_32 where available?
On x86_32, the only way to call socket(2), etc is using socketcall.
This is slated to change in Linux 4.3:
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=x86/asm&id=9dea5dc921b5f4045a18c63eb92e84dc274d17eb
If userspace adapts by preferring the direct syscalls when available,
it'll make it easier for seccomp to filter new userspace programs
(and, ideally, eventually disallow socketcall for sandbox-aware code).
Would musl be willing to detect these syscalls and use them if available?
(Code to do this probably shouldn't be committed until that change
lands in Linus' tree, just in case the syscall numbers change in the
mean time.)
--Andy
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.
