Re: [PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-26 Thread Andy Lutomirski
On Tue, Jul 17, 2012 at 4:19 PM, 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

Re: [PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-26 Thread Andy Lutomirski
On Tue, Jul 17, 2012 at 4:19 PM, Andy Lutomirski l...@amacapital.net 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

Re: [PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-18 Thread Andy Lutomirski
On Wed, Jul 18, 2012 at 11:31 AM, Will Drewry wrote: > On Tue, Jul 17, 2012 at 6:19 PM, 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

Re: [PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-18 Thread Will Drewry
On Tue, Jul 17, 2012 at 6:19 PM, 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

Re: [PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-18 Thread Will Drewry
On Tue, Jul 17, 2012 at 6:19 PM, Andy Lutomirski l...@amacapital.net 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

Re: [PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-18 Thread Andy Lutomirski
On Wed, Jul 18, 2012 at 11:31 AM, Will Drewry w...@chromium.org wrote: On Tue, Jul 17, 2012 at 6:19 PM, Andy Lutomirski l...@amacapital.net wrote: This fixes two issues that could cause incompatibility between kernel versions: - If a tracer uses SECCOMP_RET_TRACE to select a syscall number

[PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-17 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 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent

2012-07-17 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