lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 10 Jul 2014 21:06:02 -0700
From:	"H. Peter Anvin" <>
To:	Richard Guy Briggs <>,,
CC:	Paul Moore <>, Eric Paris <>,
	Al Viro <>, Will Drewry <>
Subject: Re: [PATCH 2/3] [RFC] seccomp: give BPF x32 bit when restoring x32

On 07/10/2014 08:38 PM, Richard Guy Briggs wrote:
> Commit
> 	fca460f 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 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.)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists