This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Wiring up direct socket calls on x86_32 Linux?
- From: "Tulio Magno Quites Machado Filho" <tuliom at linux dot vnet dot ibm dot com>
- To: Andy Lutomirski <luto at amacapital dot net>
- Cc: X86 ML <x86 at kernel dot org>, "linux-kernel\ at vger dot kernel dot org" <linux-kernel at vger dot kernel dot org>, 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>, Rajalakshmi Srinivasaraghavan <raji at linux dot vnet dot ibm dot com>
- Cc:
- Date: Wed, 01 Jul 2015 13:19:08 -0300
- Subject: Re: Wiring up direct socket calls on x86_32 Linux?
- Authentication-results: sourceware.org; auth=none
- References: <CALCETrUdqUm4eue2VaNPM7tkt1DSfAgo9fd-06rcys3F0q3rQA at mail dot gmail dot com>
Andy Lutomirski <luto@amacapital.net> writes:
> 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 guess you might want to follow the patch Raji sent today [1].
Her patch doesn't have all the syscalls you mentioned here, but has others too.
She will work to get a generic implementation for these functions.
[1] http://patchwork.sourceware.org/patch/7438/
--
Tulio Magno