[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87twtnx343.fsf@totoro.br.ibm.com>
Date: Wed, 01 Jul 2015 13:19:08 -0300
From: "Tulio Magno Quites Machado Filho" <tuliom@...ux.vnet.ibm.com>
To: Andy Lutomirski <luto@...capital.net>
Cc: X86 ML <x86@...nel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
Alexander Larsson <alexl@...hat.com>,
Cosimo Cecchi <cosimo@...lessm.com>,
Dan Nicholson <nicholson@...lessm.com>,
Network Development <netdev@...r.kernel.org>,
libc-alpha <libc-alpha@...rceware.org>,
Rajalakshmi Srinivasaraghavan <raji@...ux.vnet.ibm.com>
Subject: Re: Wiring up direct socket calls on x86_32 Linux?
Andy Lutomirski <luto@...capital.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists