Re: [PATCH v2 1/3] powerpc: Don't force ENOSYS as error on syscall fail

2015-02-12 Thread Purcareata Bogdan
On 12.02.2015 07:24, Michael Ellerman wrote: On Wed, 2015-02-11 at 08:36 +, Bogdan Purcareata wrote: In certain scenarios - e.g. seccomp filtering with ERRNO as default action - the system call fails for other reasons than the syscall not being available. The seccomp filter can be configured

Re: [PATCH v2 1/3] powerpc: Don't force ENOSYS as error on syscall fail

2015-02-11 Thread Michael Ellerman
On Wed, 2015-02-11 at 08:36 +, Bogdan Purcareata wrote: > In certain scenarios - e.g. seccomp filtering with ERRNO as default action - > the system call fails for other reasons than the syscall not being available. > The seccomp filter can be configured to store a user-defined error code on > r

[PATCH v2 1/3] powerpc: Don't force ENOSYS as error on syscall fail

2015-02-11 Thread Bogdan Purcareata
In certain scenarios - e.g. seccomp filtering with ERRNO as default action - the system call fails for other reasons than the syscall not being available. The seccomp filter can be configured to store a user-defined error code on return from a blacklisted syscall. Don't always set ENOSYS on do_sysc