From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tulio Magno Quites Machado Filho" Subject: Re: Wiring up direct socket calls on x86_32 Linux? Date: Wed, 01 Jul 2015 13:19:08 -0300 Message-ID: <87twtnx343.fsf@totoro.br.ibm.com> References: Mime-Version: 1.0 Content-Type: text/plain Cc: X86 ML , "linux-kernel\@vger.kernel.org" , Alexander Larsson , Cosimo Cecchi , Dan Nicholson , Network Development , libc-alpha , Rajalakshmi Srinivasaraghavan To: Andy Lutomirski Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Cc: In-Reply-To: (Andy Lutomirski's message of "Tue, 30 Jun 2015 14:14:38 -0700") List-Id: netdev.vger.kernel.org Andy Lutomirski 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