Re: [GIT pull] x86 vdso updates
From: richard -rw- weinberger
Date: Sun May 29 2011 - 12:40:41 EST
On Sun, May 29, 2011 at 5:28 PM, Andrew Lutomirski <luto@xxxxxxx> wrote:
> On Sun, May 29, 2011 at 11:10 AM, richard -rw- weinberger
> <richard.weinberger@xxxxxxxxx> wrote:
>> On Sun, May 29, 2011 at 4:57 PM, Andrew Lutomirski <luto@xxxxxxx> wrote:
>>> On Sun, May 29, 2011 at 5:51 AM, richard -rw- weinberger
>>> <richard.weinberger@xxxxxxxxx> wrote:
>>>> Yesterday I had a closer look at 64bit UML.
>>>> Glibc is always using vsyscalls because 64bit UML does not support the vDSO.
>>>>
>>>> On 32bit UML simply scans the ELF auxiliary vector provided by the host to
>>>> get the address of the vDSO.
>>>> How can I get this address on a 64bit host?
>>>
>>> I believe it's exactly the same. There's an auxv entry that points to the vDSO.
>>
>> I don't think so.
>> See:
>> http://www.win.tue.nl/~aeb/linux/lk/lk-4.html
>> Section "Address space randomization".
>> The demo program finds the vDSO only on x86.
>>
>> UML uses quite the same method to find it.
>> arch/um/os-Linux/elf_aux.c
>
> The attached program works for me.
Shouldn't it print the addresses of both AT_SYSINFO and AT_SYSINFO_EHDR?
On my x86_64 system (2.6.37) it seems to find only AT_SYSINFO_EHDR.
> I don't know what this is supposed to mean, though:
>
> /* See if the page is under TASK_SIZE */
> if (vsyscall_ehdr < (unsigned long) envp)
> vsyscall_ehdr = 0;
See commits a502a359 and 14251809.
>
> First, envp != TASK_SIZE.
>
> Second, the vDSO can be wherever it wants. On current kernels at
> least it is *always* mapped below TASK_SIZE (in the unsigned sense)
> because it's mapped into user address space.
Hmm, this would explain why UML cannot find it. :-\
--
Thanks,
//richard
--
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/