linux-kernel - Re: bug in tty ldisc and friends

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

Date:	Tue, 16 Jun 2009 11:09:37 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: bug in tty ldisc and friends


* Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > Hm, have you tried the patch i sent to you that extends the 
> > number-lock-locks-tracked limit you have run into? It is 
> > trivial.
> 
> I tried upping the number of locks a while ago - it has no effect, 
> which checking on irc seems to fit the general pattern of the 
> reports against Fedora.
> 
> The good thing is I trigger this at boot time reliably - so if 
> you've got some debug stuff you want to stick in I can do that

Could you please turn on CONFIG_DEBUG_LOCKDEP=y and after the 
overflow has happened, send us (or upload somewhere) the output of 
"cat /proc/lock*" ?

If we run out of chains then the source of the leak should be 
clearly visible in that debug outpt.

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/