From: Hans Schillstrom <hans@schillstrom.com>
To: linux-mm@kvack.org
Subject: possible slab deadlock while doing ifenslave
Date: Wed, 12 Oct 2011 10:19:52 +0200 [thread overview]
Message-ID: <201110121019.53100.hans@schillstrom.com> (raw)
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
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&(&parent->list_lock)->rlock);
lock(&(&parent->list_lock)->rlock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by ifenslave/749:
#0: (rtnl_mutex){+.+.+.}, at: [<c1321884>] rtnl_lock+0x14/0x20
#1: (&(&parent->list_lock)->rlock){-.-...}, at: [<c14234a0>] cache_flusharray+0x41/0xdb
stack backtrace:
Pid: 749, comm: ifenslave Not tainted 3.1.0-rc9+ #3
Call Trace:
[<c1421e14>] ? printk+0x2d/0x2f
[<c1076a01>] __lock_acquire+0xdc1/0x18d0
[<c1077ae2>] lock_acquire+0x82/0x1b0
[<c14234a0>] ? cache_flusharray+0x41/0xdb
[<c14291ec>] ? _raw_spin_unlock+0x2c/0x50
[<c14289e2>] _raw_spin_lock+0x42/0x50
[<c14234a0>] ? cache_flusharray+0x41/0xdb
[<c14234a0>] cache_flusharray+0x41/0xdb
[<c10fc378>] kmem_cache_free+0xa8/0x190
[<c10fc56b>] slab_destroy+0x10b/0x140
[<c10fc727>] free_block+0x187/0x1d0
[<c14234e7>] cache_flusharray+0x88/0xdb
[<c10fcc5e>] kfree+0x10e/0x220
[<f815543d>] ? rtl8169_rx_clear+0x6d/0xa0 [r8169]
[<c10fcc36>] ? kfree+0xe6/0x220
[<f815543d>] ? rtl8169_rx_clear+0x6d/0xa0 [r8169]
[<f815543d>] rtl8169_rx_clear+0x6d/0xa0 [r8169]
[<f81563a0>] rtl8169_close+0x110/0x230 [r8169]
[<c1311bd9>] __dev_close_many+0x69/0xb0
[<c1045737>] ? local_bh_enable_ip+0x67/0xd0
[<c1311c44>] __dev_close+0x24/0x40
[<c13159a2>] __dev_change_flags+0x82/0x150
[<c1321884>] ? rtnl_lock+0x14/0x20
[<c1315b11>] dev_change_flags+0x21/0x60
[<c1394140>] devinet_ioctl+0x5a0/0x710
[<c13950cd>] inet_ioctl+0x8d/0xb0
[<c12fd69f>] sock_ioctl+0x5f/0x270
[<c12fd640>] ? sock_fasync+0xd0/0xd0
[<c11180a6>] do_vfs_ioctl+0x86/0x5a0
[<c106575b>] ? up_read+0x1b/0x30
[<c102532b>] ? do_page_fault+0x18b/0x3c0
[<c1108a67>] ? fget_light+0x167/0x2f0
[<c130046c>] ? sys_socketcall+0x5c/0x2a0
[<c11185f2>] sys_ioctl+0x32/0x60
[<c1429f50>] sysenter_do_call+0x12/0x36
--
Regards
Hans Schillstrom <hans@schillstrom.com>
--
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 reply other threads:[~2011-10-12 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 8:19 Hans Schillstrom [this message]
2011-10-12 20:35 ` possible slab deadlock while doing ifenslave David Rientjes
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=201110121019.53100.hans@schillstrom.com \
--to=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 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.