linux-kernel - Re: SLUB doesn't work with kdump kernel on Cell

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: <Pine.LNX.4.64.0708141854040.1334@schroedinger.engr.sgi.com>
Date:	Tue, 14 Aug 2007 18:56:03 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Michael Ellerman <michael@...erman.id.au>
cc:	Lucio Correia <ljhc@...ibm.com>, linux-kernel@...r.kernel.org,
	Arnd Bergmann <arndb@...db.de>
Subject: Re: SLUB doesn't work with kdump kernel on Cell

On Wed, 15 Aug 2007, Michael Ellerman wrote:

> > Yes SLUB will fall back but not during bootstrap. Bootstrap needs to
> > carefully place structures on the right nodes. We fail during bootstrap
> > because there is *no* memory available on it.
> 
> Sure, you want to have the structures on the right node if possible.
> But seeing as there's no memory available, what is wrong with just
> falling back?

Then you have a useless kmem_cache_node structure that will never be used.

What I could do is an alloc without GFP_THISNODE, check the location of 
the allocated memory and then print out a big fat warning that the memory 
setup is screwed up?

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