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 22:53:42 +0100
To:	Linus Torvalds <>
Cc:	"H. Peter Anvin" <>,
	Andy Lutomirski <>,
	Linux Kernel Mailing List <>,
	Andreas Brief <>,
	Martin Runge <>
Subject: Re: [x86, vdso] BUG: unable to handle kernel paging request at

Zitat von Linus Torvalds <>:

> On Mon, Mar 10, 2014 at 2:25 PM,  <> wrote:
>> This was discovered by me.
> Sorry for the misattribution.
>> But this is not a real solution, at least when vcpu function support
>> will be added, then the code size will exceed the page size. Reserving
>> two pages for the VDSO is a good option.
> Quite frankly, there is no way in hell I will take a patch like that
> for 3.14 any more, and I would argue against it for stable.
> Now, if this problem never happens with current kernels (because it's
> purely due to the patch in -tip), then I don't much care.
> That said, I don't understand why we are even adding new features like
> this to 32-bit mode in the first place, so if that patch is the sole
> source of all this headache, then why not just throw the patch away?

The patch is working. And for this current issue there is a solution i already

A dual VDSO: a one page sized VDSO for the compat mode which has only  
the syscall
code and on multi page sized VDSO which is mapped into user space for  
the non compat

This will work and has no side effects.

- Stefani

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