Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755496AbbG1MUp (ORCPT ); Tue, 28 Jul 2015 08:20:45 -0400 Received: from mail-oi0-f46.google.com ([209.85.218.46]:35622 "EHLO mail-oi0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755445AbbG1MUn (ORCPT ); Tue, 28 Jul 2015 08:20:43 -0400 MIME-Version: 1.0 X-Originating-IP: [73.143.245.155] In-Reply-To: <1438070731-17764-1-git-send-email-drysdale@google.com> References: <1438070731-17764-1-git-send-email-drysdale@google.com> Date: Tue, 28 Jul 2015 08:20:42 -0400 Message-ID: Subject: Re: [PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs From: Paul Moore To: David Drysdale Cc: x86@kernel.org, Thomas Gleixner , Ingo Molnar , Andy Lutomirski , "H. Peter Anvin" , Michael Kerrisk , Kees Cook , Eric Paris , linux-api@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 999 Lines: 22 On Tue, Jul 28, 2015 at 4:05 AM, David Drysdale wrote: > A while ago I was trying to build a seccomp-bpf filter program that would > survive a change of x86 architecture. This was complicated for all sorts of > reasons, but one of the problems was that the different syscall numbers aren't > all available at the same time -- hence this patch. Or just use libseccomp and let it take care of all the different ABI specific warts for you. The library handles the undefined syscalls you describe, but also multiplexed syscalls (e.g. socket related syscalls on x86) and proper invalid arch/ABI filtering (you are filtering x32 correctly on x86-64 right?). * https://github.com/seccomp/libseccomp -- paul moore www.paul-moore.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/