linux-kernel - Re: [patches] [PATCH] [18/19] x86_64: Overlapping program headers in physical addr space fix

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: <453D050D.76E4.0078.0@novell.com>
Date:	Mon, 23 Oct 2006 17:08:13 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	<vgoyal@...ibm.com>
Cc:	"Andi Kleen" <ak@...e.de>, "Magnus Damm" <magnus@...inux.co.jp>,
	<linux-kernel@...r.kernel.org>, <patches@...-64.org>,
	<Ian.Campbell@...Source.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [patches] [PATCH] [18/19] x86_64: Overlapping program
	headers in physical addr space fix

>I think plain "init" also does not reflect the correct name as this section
>is also mapping .data.init_task, .data.page_aligned and .data_nosave, which
>will probably never get freed. It maps smp alternatives sections which will
>not be freed if CPU_HOTPLUG is enabled. It also maps .bss, which will never
>get freed.
>
>I think, the sections which are not being freed, should be moved up and
>made part of 'data' segment. Then create a segment 'init' for all the init
>text/data and finally create another segment say 'bss' to map bss at the
>end. How does this sound?

Superb. Though I guess .bss needs no extra segment, it should simply
be the last thing in the data segment.

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