linux-kernel - Re: [PATCH] x86_64 vDSO: use initdata

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]

Message-ID: <20080428131408.GI27997@elte.hu>
Date:	Mon, 28 Apr 2008 15:14:08 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Roland McGrath <roland@...hat.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64 vDSO: use initdata


* Roland McGrath <roland@...hat.com> wrote:

> The 64-bit vDSO image is in a special ".vdso" section for no reason I 
> can determine.  Furthermore, the location of the vdso_end symbol 
> includes some wrongly-calculated padding space in the image, which is 
> then (correctly) rounded to page size, resulting in an extra page of 
> zeros in the image mapped in to user processes.
> 
> This changes it to put the vdso.so image into normal initdata as we 
> have always done for the 32-bit vDSO images.  The extra padding is 
> gone, so the user VMA is one page instead of two.  The image that was 
> already copied around at boot time is now in initdata, so we recover 
> that wasted space after boot.

thanks Roland, applied. I suspect this will need a few days of test-time 
as we change the user-space vma layout. (not in material ways though)

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