linux-kernel - Re: [PATCH 10/28] i386: map enough initial memory to create lowmem mappings

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: <m17is3vulo.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 23 Apr 2007 12:00:51 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Chuck Ebbert <cebbert@...hat.com>, Andi Kleen <ak@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	virtualization@...ts.osdl.org, lkml <linux-kernel@...r.kernel.org>,
	Zachary Amsden <zach@...are.com>,
	Chris Wright <chrisw@...s-sol.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 10/28] i386: map enough initial memory to create lowmem mappings

"H. Peter Anvin" <hpa@...or.com> writes:

> Agreed.  However, saying that your patch shouldn't go into the mainline kernel
> until that has been fixed is spurious and wrong.  It fixes a real problem with
> minimal risk.

For a stable and frozen kernel it is probably the best we can do.

However the code is based on confusion of what should be happening and
it increases the complexity of the code and pushes us towards the edge of
code that is so crufty it is impossible to maintain.

We need to simplify this mess not make it more convoluted.

Did anyone else notice that if we don't have PAE we continue to use
the initial page tables 4K page mappings of the kernel?

This probably explains why experiments to 4MB align the i386 kernel
to improve performance failed.

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