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 returnin
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 largest
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 returnin
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
4 matches
Mail list logo