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  linux-cve-announce  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:	Thu, 20 Dec 2012 10:21:07 -0800
From:	"H. Peter Anvin" <>
To:	Stefani Seibold <>
CC:	Andy Lutomirski <>,,,,,,,,,,,
	Roland McGrath <>,
	Linus Torvalds <>,
	"H.J. Lu" <>
Subject: Re: [PATCH 6/6] Add 32 bit VDSO support for 32 and 64 bit kernels

On 12/20/2012 09:53 AM, Stefani Seibold wrote:
> In a 32 bit kernel a VDSO can mapped on an fix address VDSO_HIGH_BASE
> (kernel parameter vdso32=2 or CONFIG_COMPAT_VDSO), which is 0xffffe000.
> There is no available page BEFORE nor AFTER the page, so it is not
> possible to have VVAR or HPET as a part of that list!!!!

[Cc: Roland, Linus, H.J.]

The pages before it are safe to use, because they are kernel internal
and hence not ABI (and in fact depend on the kernel configuration
parameters.)  So pushing down the start of the fixmap region is not a
problem.  This means that to retain this compatibility the existing
entry points need to be at the end, which is more painful than we'd
like, but nevertheless there.

Do we know what actually used these fixed address, if anything, ever?


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