This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Wiring up direct socket calls on x86_32 Linux?
- From: Andy Lutomirski <luto at amacapital dot net>
- To: X86 ML <x86 at kernel dot org>, "linux-kernel at vger dot kernel dot org" <linux-kernel at vger dot kernel dot org>
- Cc: Alexander Larsson <alexl at redhat dot com>, Cosimo Cecchi <cosimo at endlessm dot com>, Dan Nicholson <nicholson at endlessm dot com>, Network Development <netdev at vger dot kernel dot org>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Tue, 30 Jun 2015 14:14:38 -0700
- Subject: Wiring up direct socket calls on x86_32 Linux?
- Authentication-results: sourceware.org; auth=none
Hi all-
sys_socketcall sucks. If nothing else, it's impossible to filter with
seccomp. Should we wire up the real socket calls so that user code
can (very slowly) start migrating?
I think the list is:
- socket
- bind
- connect
- listen
- accept4
- getsockname
- getpeername
- socketpair
- send
- sendto
- sendmsg
- recv
- recvfrom
- recvmsg
- shutdown
- setsockopt
I skipped accept, which is superseded by accept4. sendmmsg and
recvmmsg are already wired up.
Thoughts? The patch would be trivial.
Glibc people: If Linux wired up the syscalls, would glibc use them?
--Andy
--
Andy Lutomirski
AMA Capital Management, LLC