linux-kernel - Re: [CRED bug?] 2.6.29-rc3 don't survive on stress workload

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: <20090213082820.GC4606@elte.hu>
Date:	Fri, 13 Feb 2009 09:28:20 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	David Howells <dhowells@...hat.com>
Cc:	"Serge E. Hallyn" <serue@...ibm.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Lee Schermerhorn <Lee.Schermerhorn@...com>
Subject: Re: [CRED bug?] 2.6.29-rc3 don't survive on stress workload


* David Howells <dhowells@...hat.com> wrote:

> Serge E. Hallyn <serue@...ibm.com> wrote:
> 
> > 	1. put_user_ns() was being called before the uid (which
> > 	   was in the init_user_ns) was unhashed
> 
> Ah yes...  but only if CONFIG_USER_NS=y.  Otherwise the unhash was being done
> before the release anyway.  With this option set, the unhash was being deferred
> to a workqueue thread.
> 
> Okay, that seems reasonable.

Note Serge's fix also fixed a mystery hang/crash on a -tip testbox that
has been broken since the merge window. Last night it produced a straight
series of 550 bootups - previously it would crash/hang after 20-30
iterations. (i did not report it in this thread before because it's a new 
testbox with just a few weeks of track record and thus i could not exclude
potential hardware trouble)

So the bug is very much fixed.

Tested-by: Ingo Molnar <mingo@...e.hu>

	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/