On Tue, Jan 9, 2018 at 8:37 PM, Andi Kleen wrote:
> On Tue, Jan 09, 2018 at 05:26:43PM -0800, Andy Lutomirski wrote:
>>
>>
>> > On Jan 9, 2018, at 5:03 PM, Andi Kleen wrote:
>> >
>> > From: Andi Kleen
>> >
>> > In order to sanitize the system call arguments properly
>> > we need to know the numb
On Tue, Jan 09, 2018 at 05:26:43PM -0800, Andy Lutomirski wrote:
>
>
> > On Jan 9, 2018, at 5:03 PM, Andi Kleen wrote:
> >
> > From: Andi Kleen
> >
> > In order to sanitize the system call arguments properly
> > we need to know the number of syscall arguments for each
> > syscall. Add a new c
> On Jan 9, 2018, at 5:03 PM, Andi Kleen wrote:
>
> From: Andi Kleen
>
> In order to sanitize the system call arguments properly
> we need to know the number of syscall arguments for each
> syscall. Add a new column to the 32bit and 64bit syscall
> tables to list the number of arguments.
>
From: Andi Kleen
In order to sanitize the system call arguments properly
we need to know the number of syscall arguments for each
syscall. Add a new column to the 32bit and 64bit syscall
tables to list the number of arguments.
Also fix the generation script to not confuse the number
with a compa
4 matches
Mail list logo