All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: xfs lockdep trace after unlink
Date: Tue, 8 Oct 2013 17:59:47 -0400	[thread overview]
Message-ID: <20131008215947.GA8915@redhat.com> (raw)
In-Reply-To: <20131008213910.GX5790@linux.vnet.ibm.com>

On Tue, Oct 08, 2013 at 02:39:10PM -0700, Paul E. McKenney wrote:
 > On Tue, Oct 08, 2013 at 05:20:56PM -0400, Dave Jones wrote:
 > > I was deleting a kernel tree, when this happened..
 > > RCU, or xfs ?
 > > 
 > > BUG: MAX_LOCKDEP_CHAINS too low!
 > 
 > I have to ask...  What happens when you bump up MAX_LOCKDEP_CHAINS?
 
We eat up a even more memory I guess.

kernel/lockdep_internals.h:#define MAX_LOCKDEP_CHAINS_BITS	15
kernel/lockdep_internals.h:#define MAX_LOCKDEP_CHAINS	(1UL << MAX_LOCKDEP_CHAINS_BITS)

I had to increase MAX_LOCKDEP_ENTRIES on my local tree already because
I was hitting that limit. 

 > There is a patch to avoid an RCU/scheduler/perf deadlock, which may
 > be found below.  But this stack doesn't look to me to be matching that
 > deadlock.

I'll add that to my tree until it gets mainlined.

thanks,

	Dave

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: xfs lockdep trace after unlink
Date: Tue, 8 Oct 2013 17:59:47 -0400	[thread overview]
Message-ID: <20131008215947.GA8915@redhat.com> (raw)
In-Reply-To: <20131008213910.GX5790@linux.vnet.ibm.com>

On Tue, Oct 08, 2013 at 02:39:10PM -0700, Paul E. McKenney wrote:
 > On Tue, Oct 08, 2013 at 05:20:56PM -0400, Dave Jones wrote:
 > > I was deleting a kernel tree, when this happened..
 > > RCU, or xfs ?
 > > 
 > > BUG: MAX_LOCKDEP_CHAINS too low!
 > 
 > I have to ask...  What happens when you bump up MAX_LOCKDEP_CHAINS?
 
We eat up a even more memory I guess.

kernel/lockdep_internals.h:#define MAX_LOCKDEP_CHAINS_BITS	15
kernel/lockdep_internals.h:#define MAX_LOCKDEP_CHAINS	(1UL << MAX_LOCKDEP_CHAINS_BITS)

I had to increase MAX_LOCKDEP_ENTRIES on my local tree already because
I was hitting that limit. 

 > There is a patch to avoid an RCU/scheduler/perf deadlock, which may
 > be found below.  But this stack doesn't look to me to be matching that
 > deadlock.

I'll add that to my tree until it gets mainlined.

thanks,

	Dave


  reply	other threads:[~2013-10-08 21:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 21:20 xfs lockdep trace after unlink Dave Jones
2013-10-08 21:20 ` Dave Jones
2013-10-08 21:37 ` Dave Chinner
2013-10-08 21:37   ` Dave Chinner
2013-10-08 21:54   ` Paul E. McKenney
2013-10-08 21:54     ` Paul E. McKenney
2013-10-08 22:25     ` Dave Chinner
2013-10-08 22:25       ` Dave Chinner
2013-10-08 23:01       ` Paul E. McKenney
2013-10-08 23:01         ` Paul E. McKenney
2013-10-08 21:39 ` Paul E. McKenney
2013-10-08 21:39   ` Paul E. McKenney
2013-10-08 21:59   ` Dave Jones [this message]
2013-10-08 21:59     ` Dave Jones

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=20131008215947.GA8915@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=xfs@oss.sgi.com \
    /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.