linux-kernel - Re: [PATCH 0/4] Add 32 bit VDSO time function support

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1391097131.2898.5.camel@wall-e.seibold.net>
Date:	Thu, 30 Jan 2014 16:52:11 +0100
From:	Stefani Seibold <stefani@...bold.net>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	gregkh@...uxfoundation.org, 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,
	luto@...capital.net, xemul@...allels.com, gorcunov@...nvz.org,
	andriy.shevchenko@...ux.intel.com, Martin.Runge@...de-schwarz.com,
	Andreas.Brief@...de-schwarz.com
Subject: Re: [PATCH 0/4] Add 32 bit VDSO time function support

Am Donnerstag, den 30.01.2014, 07:31 -0800 schrieb H. Peter Anvin:
> On 01/30/2014 02:49 AM, stefani@...bold.net wrote:
> > The VDSO page for a 32 bit resided now on 0xffffc000, followed by the VVAR and
> > HPET page.
> 
> Any reason to not move the vdso base page to the top, in order to avoid
> breaking broken applications?  It seems a fairly innocuous shuffle...
> probably little gain, but very little cost.
> 
> 	-hpa
> 

The reason is that i get need than an additional VMA for HPET and VVAR. 

I seen no break of applications since the __FIXADDR_TOP is not on a fix
place. Lguest, XEN, OPLC and the reservetop Kernel Parameter will change
the VDSO Page Address.

- Stefani

--
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/