From: "Tulio Magno Quites Machado Filho" <tuliom@linux.vnet.ibm.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: X86 ML <x86@kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexander Larsson <alexl@redhat.com>,
Cosimo Cecchi <cosimo@endlessm.com>,
Dan Nicholson <nicholson@endlessm.com>,
Network Development <netdev@vger.kernel.org>,
libc-alpha <libc-alpha@sourceware.org>,
Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>
Subject: Re: Wiring up direct socket calls on x86_32 Linux?
Date: Wed, 01 Jul 2015 13:19:08 -0300 [thread overview]
Message-ID: <87twtnx343.fsf@totoro.br.ibm.com> (raw)
In-Reply-To: <CALCETrUdqUm4eue2VaNPM7tkt1DSfAgo9fd-06rcys3F0q3rQA@mail.gmail.com> (Andy Lutomirski's message of "Tue, 30 Jun 2015 14:14:38 -0700")
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
prev parent reply other threads:[~2015-07-01 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:14 Wiring up direct socket calls on x86_32 Linux? Andy Lutomirski
2015-06-30 21:29 ` Andreas Schwab
2015-07-01 16:19 ` Tulio Magno Quites Machado Filho [this message]
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=87twtnx343.fsf@totoro.br.ibm.com \
--to=tuliom@linux.vnet.ibm.com \
--cc=alexl@redhat.com \
--cc=cosimo@endlessm.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=nicholson@endlessm.com \
--cc=raji@linux.vnet.ibm.com \
--cc=x86@kernel.org \
/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.
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).