linux-kernel - Re: randconfig build error with next-20140512, in mm/slub.c

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]

Date:	Mon, 12 May 2014 13:36:53 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Pekka Enberg <penberg@....fi>
cc:	Christoph Lameter <cl@...ux.com>, Jim Davis <jim.epost@...il.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next <linux-next@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>, penberg@...nel.org,
	mpm@...enic.com, linux-mm@...ck.org
Subject: Re: randconfig build error with next-20140512, in mm/slub.c

On Mon, 12 May 2014, Pekka Enberg wrote:

> On 05/12/2014 09:47 PM, Christoph Lameter wrote:
> > A patch was posted today for this issue.
> 
> AFAICT, it's coming from -mm. Andrew, can you pick up the fix?
> 
> > Date: Mon, 12 May 2014 09:36:30 -0300
> > From: Fabio Estevam <fabio.estevam@...escale.com>
> > To: akpm@...ux-foundation.org
> > Cc: linux-mm@...ck.org, festevam@...il.com, Fabio Estevam
> > <fabio.estevam@...escale.com>,    Christoph Lameter <cl@...ux.com>, David
> > Rientjes <rientjes@...gle.com>, Pekka Enberg <penberg@...nel.org>
> > Subject: [PATCH] mm: slub: Place count_partial() outside CONFIG_SLUB_DEBUG
> > if block
> > 

That's the wrong fix since it doesn't work properly when sysfs is 
disabled.  We want http://marc.info/?l=linux-mm-commits&m=139992385527040 
which was merged into -mm already.
--
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/