linux-kernel - Re: [PATCH 6/6] Add 32 bit VDSO support for 32 and 64 bit kernels

lists.openwall.net		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] [day] [month] [year] [list]

Date:	Thu, 20 Dec 2012 10:40:59 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Roland McGrath <mcgrathr@...gle.com>
CC:	"H.J. Lu" <hjl.tools@...il.com>,
	Stefani Seibold <stefani@...bold.net>,
	Andy Lutomirski <luto@...capital.net>,
	linux-kernel@...r.kernel.org, x86@...nel.org, tglx@...utronix.de,
	mingo@...hat.com, ak@...ux.intel.com, aarcange@...hat.com,
	john.stultz@...aro.org, xemul@...allels.com, gorcunov@...nvz.org,
	andriy.shevchenko@...ux.intel.com,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	jakub@...hat.com
Subject: Re: [PATCH 6/6] Add 32 bit VDSO support for 32 and 64 bit kernels

On 12/20/2012 10:35 AM, Roland McGrath wrote:
> The Kconfig text for COMPAT_VDSO suggests that glibc versions prior to
> 2.3.3 may have relied on the fixed address.  I can't find anything in the
> libc revision history to explain that (AFAIK the code always used
> AT_SYSINFO* since it started using the vDSO at all), but it might have been
> something less obvious.  Someone like Jakub might recall the details.

Jakub, any insights?

We're trying to figure out if anything ever depended on the COMPAT_VDSO
(at a fixed address), in particular for i386 (as opposed to x86-64).

	-hpa


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/