linux-kernel - Re: [PATCH 4/7] x86, mm: only keep initial mapping for ram

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]

Date:	Wed, 10 Oct 2012 07:59:41 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, Jacob Shin <jacob.shin@....com>,
	Tejun Heo <tj@...nel.org>,
	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/7] x86, mm: only keep initial mapping for ram

On Wed, Oct 10, 2012 at 6:48 AM, Konrad Rzeszutek Wilk
<konrad@...nel.org> wrote:
> On Tue, Oct 09, 2012 at 04:58:32PM -0700, Yinghai Lu wrote:
>> 0 mean any e820 type will be kept, and only hole is removed.
>>
>> change to E820_RAM and E820_RESERVED_KERN only.
>>
>
> This is good candidate for squashing in-to the previous patch, with
> verbose explanation why you care only about those two types.

two patches should be more safe.

new series will make sure only map RAM/RESEVED_KERN, so we should only
keep initial page table with those types.
--
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/