Re: [PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs

2015-07-28 Thread Paul Moore
On Tue, Jul 28, 2015 at 11:32 AM, David Drysdale wrote: > On Tue, Jul 28, 2015 at 1:20 PM, Paul Moore wrote: >> 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

Re: [PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs

2015-07-28 Thread David Drysdale
On Tue, Jul 28, 2015 at 1:20 PM, Paul Moore wrote: > 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 probl

Re: [PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs

2015-07-28 Thread Paul Moore
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 a

[PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs

2015-07-28 Thread David Drysdale
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. Naming-wise, And