Re: [PATCH v2 resend] seccomp: Make syscall skipping and nr changes more consistent

2012-10-02 Thread James Morris
On Mon, 1 Oct 2012, Andy Lutomirski wrote: > This fixes two issues that could cause incompatibility between > kernel versions: > > - If a tracer uses SECCOMP_RET_TRACE to select a syscall number >higher than the largest known syscall, emulate the unknown >vsyscall by returning -ENOSYS.

Re: [PATCH v2 resend] seccomp: Make syscall skipping and nr changes more consistent

2012-10-02 Thread James Morris
On Mon, 1 Oct 2012, Andy Lutomirski wrote: This fixes two issues that could cause incompatibility between kernel versions: - If a tracer uses SECCOMP_RET_TRACE to select a syscall number higher than the largest known syscall, emulate the unknown vsyscall by returning -ENOSYS. (This

[PATCH v2 resend] seccomp: Make syscall skipping and nr changes more consistent

2012-10-01 Thread Andy Lutomirski
This fixes two issues that could cause incompatibility between kernel versions: - If a tracer uses SECCOMP_RET_TRACE to select a syscall number higher than the largest known syscall, emulate the unknown vsyscall by returning -ENOSYS. (This is unlikely to make a noticeable difference on

[PATCH v2 resend] seccomp: Make syscall skipping and nr changes more consistent

2012-10-01 Thread Andy Lutomirski
This fixes two issues that could cause incompatibility between kernel versions: - If a tracer uses SECCOMP_RET_TRACE to select a syscall number higher than the largest known syscall, emulate the unknown vsyscall by returning -ENOSYS. (This is unlikely to make a noticeable difference on