From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Christoph Lameter <cl@linux.com>
Cc: Yong Zhang <yong.zhang0@gmail.com>,
linux-kernel@vger.kernel.org, Pekka Enberg <penberg@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
cl@gentwo.org
Subject: Re: 3.2-rc1: INFO: possible recursive locking detected
Date: Fri, 11 Nov 2011 07:48:45 -0800 [thread overview]
Message-ID: <20111111154845.GA2283@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1111110841470.3006@router.home>
On Fri, Nov 11, 2011 at 08:43:13AM -0600, Christoph Lameter wrote:
> On Thu, 10 Nov 2011, Paul E. McKenney wrote:
>
> > On Wed, Nov 09, 2011 at 05:05:57PM +0800, Yong Zhang wrote:
> > > Hi,
> > >
> > > Just get below waring when doing:
> > > for i in `seq 1 10`; do ./perf bench -f simple sched messaging -g 40; done
> > >
> > > And kernel config is attached.
> >
> > This appears to me to be the same false positive from the slab allocator
> > that has been seen before. Christoph, any progress on this?
>
> No this is another issue because it is not SLAB but SLUB. Must be a bug
> introduced by the recent merges of the per cpu partial list support.
Ah, OK. Thank you for looking this over and for the suggested solutions!
Thanx, Paul
next prev parent reply other threads:[~2011-11-11 15:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 9:05 3.2-rc1: INFO: possible recursive locking detected Yong Zhang
2011-11-09 9:09 ` Yong Zhang
2011-11-10 23:35 ` INFO: possible recursive locking detected: get_partial_node() on 3.2-rc1 Julie Sullivan
2011-11-10 23:35 ` Julie Sullivan
2011-11-11 3:04 ` Shaohua Li
2011-11-11 3:04 ` Shaohua Li
2011-11-11 4:42 ` Yong Zhang
2011-11-11 4:42 ` Yong Zhang
2011-11-11 14:57 ` Christoph Lameter
2011-11-11 14:57 ` Christoph Lameter
2011-11-11 15:02 ` Christoph Lameter
2011-11-11 15:02 ` Christoph Lameter
2011-11-11 19:09 ` Julie Sullivan
2011-11-11 19:09 ` Julie Sullivan
2011-11-11 19:22 ` Paul E. McKenney
2011-11-11 19:22 ` Paul E. McKenney
2011-11-14 5:34 ` Shaohua Li
2011-11-14 5:34 ` Shaohua Li
2011-11-15 7:22 ` Yong Zhang
2011-11-15 7:22 ` Yong Zhang
2011-11-15 18:49 ` Pekka Enberg
2011-11-15 18:49 ` Pekka Enberg
2011-11-15 16:02 ` Christoph Lameter
2011-11-15 16:02 ` Christoph Lameter
2011-11-10 23:47 ` 3.2-rc1: INFO: possible recursive locking detected Paul E. McKenney
2011-11-11 14:43 ` Christoph Lameter
2011-11-11 15:48 ` Paul E. McKenney [this message]
2011-11-11 13:41 ` INFO: possible recursive locking detected: do_lookup() on 3.2-rc1 Shawn Guo
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=20111111154845.GA2283@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=cl@gentwo.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
--cc=yong.zhang0@gmail.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.