From: David Rientjes <rientjes@google.com>
To: Hans Schillstrom <hans@schillstrom.com>
Cc: linux-mm@kvack.org
Subject: Re: possible slab deadlock while doing ifenslave
Date: Wed, 12 Oct 2011 13:35:51 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1110121333560.7646@chino.kir.corp.google.com> (raw)
In-Reply-To: <201110121019.53100.hans@schillstrom.com>
On Wed, 12 Oct 2011, Hans Schillstrom wrote:
> Hello,
> I got this when I was testing a VLAN patch i.e. using Dave Millers net-next from today.
> When doing this on a single core i686 I got the warning every time,
> however ifenslave is not hanging it's just a warning
> Have not been testing this on a multicore jet.
>
> There is no warnings with a 3.0.4 kernel.
>
> Is this a known warning ?
>
> ~ # ifenslave bond0 eth1 eth2
>
> =============================================
> [ INFO: possible recursive locking detected ]
> 3.1.0-rc9+ #3
> ---------------------------------------------
> ifenslave/749 is trying to acquire lock:
> (&(&parent->list_lock)->rlock){-.-...}, at: [<c14234a0>] cache_flusharray+0x41/0xdb
>
> but task is already holding lock:
> (&(&parent->list_lock)->rlock){-.-...}, at: [<c14234a0>] cache_flusharray+0x41/0xdb
>
Hmm, the only candidate that I can see that may have caused this is
83835b3d9aec ("slab, lockdep: Annotate slab -> rcu -> debug_object ->
slab"). Could you try reverting that patch in your local tree and seeing
if it helps?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-12 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 8:19 Hans Schillstrom
2011-10-12 20:35 ` David Rientjes [this message]
2011-10-13 8:19 ` Hans Schillstrom
2011-10-13 23:03 ` David Rientjes
2011-10-13 23:21 ` Peter Zijlstra
2011-10-14 6:30 ` Hans Schillstrom
2011-11-28 21:19 ` Peter Zijlstra
2011-11-28 21:20 ` Peter Zijlstra
2011-11-29 14:58 ` Christoph Lameter
2011-11-29 15:38 ` Peter Zijlstra
2011-11-29 14:55 ` Christoph Lameter
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=alpine.DEB.2.00.1110121333560.7646@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=hans@schillstrom.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox