Re: [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall= parameter

From: H. Peter Anvin
Date: Wed Aug 10 2011 - 17:16:19 EST


Andrew Lutomirski <luto@xxxxxxx> wrote:

>On Wed, Aug 10, 2011 at 1:21 PM, H. Peter Anvin <hpa@xxxxxxxxx> wrote:
>> On 08/10/2011 10:15 AM, Andy Lutomirski wrote:
>>> There are three choices:
>>>
>>> vsyscall=native: Vsyscalls are native code that issues the
>>> corresponding syscalls.
>>>
>>> vsyscall=emulate (default): Vsyscalls are emulated by instruction
>>> fault traps, tested in the bad_area path. ÂThe actual contents of
>>> the vsyscall page is the same as the vsyscall=native case except
>>> that it's marked NX. ÂThis way programs that make assumptions about
>>> what the code in the page does will not be confused when they read
>>> that code.
>>>
>>> vsyscall=none: Trying to execute a vsyscall will segfault.
>>>
>>> Signed-off-by: Andy Lutomirski <luto@xxxxxxx>
>>
>> Hi Andy,
>>
>> This patch doesn't apply. ÂWhat is your baseline for this patch?
>
>My baseline was a commit that probably only lives in my tree, but the
>patches should apply cleanly on top of
>c149a665ac488e0dac22a42287f45ad1bda06ff1, which is the current
>tip/x86/vdso.
>
>--Andy

Please rebase your patch on the current -linus since it appears to have changed since x86/vdso was merged.

-hpa
--
Sent from my mobile phone. Please excuse my brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/