From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754733AbbGAQT1 (ORCPT <rfc822;w@1wt.eu>);
	Wed, 1 Jul 2015 12:19:27 -0400
Received: from e24smtp01.br.ibm.com ([32.104.18.85]:58442 "EHLO
	e24smtp01.br.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754566AbbGAQTS (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 1 Jul 2015 12:19:18 -0400
X-Helo: d24dlp01.br.ibm.com
X-MailFrom: tuliom@linux.vnet.ibm.com
X-RcptTo: netdev@vger.kernel.org
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?
References: <CALCETrUdqUm4eue2VaNPM7tkt1DSfAgo9fd-06rcys3F0q3rQA@mail.gmail.com>
Date: Wed, 01 Jul 2015 13:19:08 -0300
In-Reply-To: <CALCETrUdqUm4eue2VaNPM7tkt1DSfAgo9fd-06rcys3F0q3rQA@mail.gmail.com>
	(Andy Lutomirski's message of "Tue, 30 Jun 2015 14:14:38 -0700")
Message-ID: <87twtnx343.fsf@totoro.br.ibm.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.51 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15070116-1524-0000-0000-000002FE812E
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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