lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 10 Mar 2014 07:59:38 -0700
From:	"H. Peter Anvin" <>
To:	Andy Lutomirski <>
CC:	Stefani Seibold <>,
	"" <>,
	Martin Runge <>,
	Andreas Brief <>,
	Linus Torvalds <>
Subject: Re: [x86, vdso] BUG: unable to handle kernel paging request at d34bd000

On 03/09/2014 09:46 PM, Andy Lutomirski wrote:
> On Sun, Mar 9, 2014 at 8:18 PM, Andy Lutomirski <> wrote:
>> (Of course, I haven't the faintest idea what l_addr in glibc means.
>> If there was a way to arrange for l_addr to be zero, then maybe none
>> of this would matter.  Hmm, I wonder if just not relocating the vdso
>> at all would have the desired effect.  Anyone out there understand
>> glibc?)
> No, that won't work.  The bug is that glibc expects PT_DYNAMIC's vaddr
> to be the virtual address of the dynamic table.  This can only be true
> if the vdso is mapped at the address that the kernel relocated it to.
> I also learned that glibc's code is really hideous.  Wow.

At the same time it does mean we have more flexibility than having a
hard-coded address... we can at least allocate more than one page in the
fixmap; for a really "full service" solution the kernel could adjust the
vdso for whatever address the "fixmap" is at.

I have mentioned in the past wanting to move the fixmap to the low part
of the kernel space, because the top isn't really fixed...


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists