linux-kernel - Re: [PATCH 04/19] 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]

Message-ID: <CAE9FiQWEhfOPOqSQLK9rkjvJw+wEoBYKGiKTFdeXqt8jrF=jCQ@mail.gmail.com>
Date:	Mon, 22 Oct 2012 10:43:57 -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 04/19] x86, mm: only keep initial mapping for ram

On Mon, Oct 22, 2012 at 7:33 AM, Konrad Rzeszutek Wilk
<konrad@...nel.org> wrote:
> On Thu, Oct 18, 2012 at 01:50:15PM -0700, Yinghai Lu wrote:
>> 0 mean any e820 type, for any range is overlapped with any entry in e820,
>> kernel will keep it's initial page table mapping.
>>
>> What we want is only keeping initial page table for ram range.
>
> Can you squash it in the previous patch then pls? It seems like
> this is a bug-fix to a bug-fix. And since this patchset is still
> out-side the Linus's tree you have the option of squashing/rebasing.

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