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] [day] [month] [year] [list]
Message-ID: <OF94FA6DBC.7FC9A140-ON48257672.00081DD4-48257672.000909A3@sunplusct.com>
Date:	Wed, 18 Nov 2009 09:37:50 +0800
From:	liqin.chen@...plusct.com
To:	steve@...idescorp.com
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	David Howells <dhowells@...hat.com>,
	Greg Ungerer <gerg@...pgear.com>,
	Lennox Wu <lennox.wu@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] microblaze: Fix pfn_valid() for noMMU

"Steven J. Magnani" <steve@...idescorp.com> 写于 2009-11-17 22:27:54:

> On Mon, 2009-11-16 at 14:14 -0800, Andrew Morton wrote:
> > On Fri, 13 Nov 2009 16:08:29 -0600
> > steve@...idescorp.com wrote:
> > 
> > > Configuring DEBUG_SLAB causes a noMMU kernel to die during 
initialization
> > > with an invalid virtual address panic in kfree_debugcheck().
> > > The panic is due to an improper definition of pfn_valid().
> > > 
> > > ...
> > Is arch/score/include/asm/page.h buggy also?
> > 
> 
> I don't believe so, but only because MEMORY_START is defined as zero for
> that arch, making min_low_pfn zero.
> 

Yes, it's right because MEMORY_START is defined as 0,
make min_low_pfn to zero and max_mapnr equal max_low_pfn.

We will fix it to make code more clear.

liqin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ