linux-kernel - Re: linux-next -> 2.6.34: Tree for April 28 (logfs)

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:	Tue, 18 May 2010 02:40:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jörn Engel <joern@...fs.org>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	logfs@...fs.org
Subject: Re: linux-next -> 2.6.34: Tree for April 28 (logfs)


* Jörn Engel <joern@...fs.org> wrote:

> On Sun, 16 May 2010 20:48:26 -0700, Randy Dunlap wrote:
> > 
> > This fix is now needed in 2.6.34....
> 
> I didn't send Linus a pull request, as I was on 
> vacation last week.  Bad timing, given the 2.6.34 
> release date. :(

Dont worry about it too much - the likehood of the 
build failure was very low, around 1:50 in my 
randconfig tests. I doubt any real user ran into this 
spontaenously - and randconfig folks know how to fix 
rare build failures :-)

You might still want to forward the commit to 
-stable, once it's in Linus's tree.

Thanks,

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