From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 2/3] [RFC] seccomp: give BPF x32 bit when restoring x32 filter Date: Thu, 10 Jul 2014 21:06:02 -0700 Message-ID: <53BF62AA.20105@zytor.com> References: <6a69eb94b4cfac5f94b229c2eb2ebc402aac722a.1405023592.git.rgb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <6a69eb94b4cfac5f94b229c2eb2ebc402aac722a.1405023592.git.rgb@redhat.com> Sender: linux-kernel-owner@vger.kernel.org To: Richard Guy Briggs , linux-audit@redhat.com, linux-kernel@vger.kernel.org Cc: Paul Moore , Eric Paris , Al Viro , Will Drewry List-Id: linux-audit@redhat.com On 07/10/2014 08:38 PM, Richard Guy Briggs wrote: > Commit > fca460f hpa@zytor.com 2012-02-19 07:56:26 -0800 > x32: Handle the x32 system call flag > > provided a method to multiplex architecture with the syscall number for X32 > calls. > > Commit > 8b4b9f2 pmoore@redhat.com 2013-02-15 12:21:43 -0500 > x86: remove the x32 syscall bitmask from syscall_get_nr() > > broke audit and potentially other users of syscall_get_nr() which depend on > that call as named. > > Commit > audit: add AUDIT_ARCH_X86_X32 arch definition > > is required to provide the new ARCH definition AUDIT_ARCH_X86_X32 for > syscall_get_arch(). > > This patch along with reverting 8b4b9f2 should satisfy other regular users of > syscall_get_nr() without changing the seccomp interface to BPF. > Incidentally: do seccomp users know that on an x86-64 system you can recevie system calls from any of the x86 architectures, regardless of how the program is invoked? (This is unusual, so normally denying those "alien" calls is the right thing to do.) -hpa