linux-kernel - Re: [BUG] sysrq-m oops

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 07 Jun 2007 12:54:41 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Bob Picco <bob.picco@...com>
Cc:	Chuck Ebbert <cebbert@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Sripathi Kodi <sripathik@...ibm.com>,
	Bernhard Walle <bwalle@...e.de>, acme@...hat.com,
	apw@...dowen.org
Subject: Re: [BUG] sysrq-m oops

On Thu, 2007-06-07 at 14:21 -0400, Bob Picco wrote:
> Chuck Ebbert wrote:	[Thu Jun 07 2007, 11:42:38AM EDT]
> > On 06/06/2007 08:27 PM, john stultz wrote:
> > > Hey All,
> > > 	With 2.6.21 and the current -git, we're seeing the following oops when
> > > we try sysrq-m:
> > > 
> > 
> > It's here in arch/x86_64/mm/init.c::show_mem():
> > 
> >         for_each_online_pgdat(pgdat) {
> >                for (i = 0; i < pgdat->node_spanned_pages; ++i) {
> This is probably with sparsemem? I'm working with acme@...hat.com to
> test a patch. Basically you need to validate the pfn because it
> could be in a hole. Most arches which support sparsemem perform this
> check.
> 
> 			if (!pfn_valid(pgdat->node_start_pfn + i))
> 				continue;


Yep. That catch avoids the issue! Sounds like a 2.6.21.x candidate.

thanks so much!
-john


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