Le 26/03/2020 à 13:06, Michael Ellerman a écrit :
On Wed, 2020-03-04 at 11:04:02 UTC, Michael Ellerman wrote:
There's two different paths through the sigreturn code, depending on
whether the VDSO is mapped or not. We recently discovered a bug in the
unmapped case, because it's not commonly
On Wed, 2020-03-04 at 11:04:02 UTC, Michael Ellerman wrote:
> There's two different paths through the sigreturn code, depending on
> whether the VDSO is mapped or not. We recently discovered a bug in the
> unmapped case, because it's not commonly used these days.
>
> So add a test that sends
Nathan Lynch writes:
> Nathan Lynch writes:
>> Michael Ellerman writes:
>>> +static int search_proc_maps(char *needle, unsigned long *low, unsigned
>>> long *high)
>>
>>^^ const?
Sorry I meant to do this but then forgot.
>>> +{
>>> + unsigned long start,
Nathan Lynch writes:
> Michael Ellerman writes:
>
>> +static int search_proc_maps(char *needle, unsigned long *low, unsigned long
>> *high)
>
>^^ const?
>
>> +{
>> +unsigned long start, end;
>> +static char buf[4096];
>> +
Michael Ellerman writes:
> +static int search_proc_maps(char *needle, unsigned long *low, unsigned long
> *high)
^^ const?
> +{
> + unsigned long start, end;
> + static char buf[4096];
> + char name[128];
> + FILE
There's two different paths through the sigreturn code, depending on
whether the VDSO is mapped or not. We recently discovered a bug in the
unmapped case, because it's not commonly used these days.
So add a test that sends itself a signal, then moves the VDSO, takes
another signal and finally
