linux-kernel - Re: linux-next: slab tree build failure

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] [day] [month] [year] [list]

Message-Id: <1245661742.18751.32.camel@penberg-laptop>
Date:	Mon, 22 Jun 2009 12:09:02 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Christoph Lameter <cl@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: slab tree build failure

On Fri, 2009-06-19 at 20:40 +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2009-06-19 at 14:16 +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> > 
> > mm/slqb.c:75: error: 'SLAB_GFP_BOOT_MASK' undeclared here (not in a function)
> > 
> > Caused by commit df548b0bbaf2d4d16ce52d2f5ccdc1cfded70e06 ("SLQB: Fix
> > early boot allocations") from the slab tree interacting with commit
> > dcce284a259373f9e5570f2e33f79eca84fcf565 ("mm: Extend gfp masking to the
> > page allocator") that entered Linus' tree today.
> > 
> > I have applied this patch for today:
> 
> The right fix is to remove slab_gfp_mask from slqb.c and use
> the global gfp_allowed_mask instead.

This should be fixed now in slab.git. Something in SQLB is still
enabling interrupts during early boot but I don't have the time to look
at it in more detail right now.

			Pekka

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