linux-kernel - Re: [patch] mm: sparsemem memory_present() memory corruption 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440804151733h414209fcvf38e83fb5c5ec15d@mail.gmail.com>
Date:	Tue, 15 Apr 2008 17:33:37 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Christoph Lameter" <clameter@....com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Pekka Enberg" <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, "Mel Gorman" <mel@....ul.ie>,
	"Nick Piggin" <npiggin@...e.de>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, apw@...dowen.org,
	"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [patch] mm: sparsemem memory_present() memory corruption fix

On Tue, Apr 15, 2008 at 5:19 PM, Christoph Lameter <clameter@....com> wrote:
> On Wed, 16 Apr 2008, Ingo Molnar wrote:
>
>  > if a !PAE x86 kernel is booted on a 32-bit system with more than
>  > 4GB of RAM, then we call memory_present() with a start/end that
>  > goes outside the scope of MAX_PHYSMEM_BITS.
>
>  Well okay this fixes it but is this the right fix? The arch should not
>  call memory_present() with an invalid pfn.

yes in find_max_pfn...

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