All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: bug in tty ldisc and friends
Date: Tue, 16 Jun 2009 11:09:37 +0200	[thread overview]
Message-ID: <20090616090937.GE13771@elte.hu> (raw)
In-Reply-To: <20090616095706.36f01282@lxorguk.ukuu.org.uk>


* Alan Cox <alan@lxorguk.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

  reply	other threads:[~2009-06-16  9:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  5:45 bug in tty ldisc and friends Steven Rostedt
2009-06-16  8:37 ` Alan Cox
2009-06-16  8:50   ` Ingo Molnar
2009-06-16  8:57     ` Alan Cox
2009-06-16  9:09       ` Ingo Molnar [this message]
2009-06-16 10:00       ` Ingo Molnar
2009-06-16 10:04         ` Alan Cox
2009-06-16 10:12           ` Ingo Molnar
2009-06-16 10:25             ` Ingo Molnar
2009-06-16 10:29               ` Ingo Molnar
2009-06-16 10:34                 ` Joerg Roedel
2009-06-16 10:45                   ` Ingo Molnar
2009-06-16 10:36                 ` Ingo Molnar
2009-06-16 11:39                   ` Joerg Roedel
2009-06-16 12:11                     ` Ingo Molnar
2009-06-16 15:24                   ` Joerg Roedel
2009-06-17  8:32                   ` Peter Zijlstra
2009-06-17 14:10                     ` Ingo Molnar
2009-06-17 14:28                       ` Joerg Roedel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090616090937.GE13771@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.