linux-kernel - Re: linux-next: Tree for March 16 (slob)

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]

Date:	Wed, 18 Mar 2009 08:49:36 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Nick Piggin <npiggin@...e.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: linux-next: Tree for March 16 (slob)

On Tue, 17 Mar 2009 10:29:02 +0100 Ingo Molnar wrote:

> 
> * Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > On Mon, 16 Mar 2009 11:32:00 -0700 Randy Dunlap <randy.dunlap@...cle.com> wrote:
> > >
> > > mm/slob.c:480: error: 'flags' undeclared (first use in this function)
> > > 
> > > pseudo-patch:
> > > 
> > > s/flags/gfp/
> > 
> > Caused by commit cf40bd16fdad42c053040bcd3988f5fdedbb6c57 ("lockdep:
> > annotate reclaim context (__GFP_NOFS)") from the tracing tree.
> > 
> > Now fixed in the tip tree.
> 
> Note this has been broken for a relatively long time and only 
> got fixed when i noticed that randconfig was not as random as it 
> was supposed to be. That's how it started triggering in 
> linux-next too i suspect.


linux-next of 20090318 still has this build error.
Is the fix in some branch that is not merged into linux-next?

Thanks,
---
~Randy
--
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/