The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: "John W. Linville" <linville@tuxdriver.com>,
	David Miller <davem@davemloft.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Circular locking (rtnl_mutex & _xmit_IEEE80211) during suspend
Date: Sun, 03 Aug 2008 11:35:27 -0700	[thread overview]
Message-ID: <4895FA6F.8050209@qualcomm.com> (raw)

Got this lockdep complaint yesterday

--

wlan0: disassociating by local choice (reason=3)

=============================================
[ INFO: possible recursive locking detected ]
2.6.27-rc1 #29
---------------------------------------------
NetworkManager/1744 is trying to acquire lock:
 (_xmit_IEEE80211#2){-+..}, at: [<ffffffff804b18ea>] dev_deactivate+0x9a/0x150

but task is already holding lock:
 (_xmit_IEEE80211#2){-+..}, at: [<ffffffff804b18ea>] dev_deactivate+0x9a/0x150

other info that might help us debug this:
2 locks held by NetworkManager/1744:
 #0:  (rtnl_mutex){--..}, at: [<ffffffff804ac8fa>] rtnetlink_rcv+0x1a/0x40
 #1:  (_xmit_IEEE80211#2){-+..}, at: [<ffffffff804b18ea>]
dev_deactivate+0x9a/0x150

stack backtrace:
Pid: 1744, comm: NetworkManager Not tainted 2.6.27-rc1 #29

Call Trace:
 [<ffffffff80261dcf>] __lock_acquire+0x92f/0x1020
 [<ffffffff80260dfd>] ? trace_hardirqs_on+0xd/0x10
 [<ffffffff80260dd1>] ? trace_hardirqs_on_caller+0xe1/0x100
 [<ffffffff804b15cb>] ? dev_deactivate_queue+0x4b/0x60
 [<ffffffff802406ed>] ? local_bh_disable+0xd/0x10
 [<ffffffff8026251b>] lock_acquire+0x5b/0x80
 [<ffffffff804b18ea>] ? dev_deactivate+0x9a/0x150
 [<ffffffff80532f6f>] _spin_lock+0x2f/0x40
 [<ffffffff804b18ea>] dev_deactivate+0x9a/0x150
 [<ffffffff804a2955>] dev_close+0x55/0xb0
 [<ffffffff8050777d>] ieee80211_stop+0x36d/0x450
 [<ffffffff804a2966>] dev_close+0x66/0xb0
 [<ffffffff804a2541>] dev_change_flags+0xa1/0x1e0
 [<ffffffff804ab6ac>] do_setlink+0x20c/0x3a0
 [<ffffffff805366e0>] ? sub_preempt_count+0x80/0xd0
 [<ffffffff80532ce0>] ? _read_unlock+0x30/0x60
 [<ffffffff804aba0d>] rtnl_setlink+0x10d/0x150
 [<ffffffff804acaad>] rtnetlink_rcv_msg+0x18d/0x240
 [<ffffffff804ac920>] ? rtnetlink_rcv_msg+0x0/0x240
 [<ffffffff804b52b9>] netlink_rcv_skb+0x89/0xb0
 [<ffffffff804ac909>] rtnetlink_rcv+0x29/0x40
 [<ffffffff804b4e59>] ? netlink_sendmsg+0x139/0x2d0
 [<ffffffff804b4d0d>] netlink_unicast+0x2cd/0x2e0
 [<ffffffff8049b9de>] ? __alloc_skb+0x6e/0x150
 [<ffffffff804b4ef3>] netlink_sendmsg+0x1d3/0x2d0
 [<ffffffff80493a0f>] sock_sendmsg+0xdf/0x110
 [<ffffffff80251a70>] ? autoremove_wake_function+0x0/0x40
 [<ffffffff80260dfd>] ? trace_hardirqs_on+0xd/0x10
 [<ffffffff80260dd1>] ? trace_hardirqs_on_caller+0xe1/0x100
 [<ffffffff80260dfd>] ? trace_hardirqs_on+0xd/0x10
 [<ffffffff802b7c2e>] ? fget_light+0xce/0xe0
 [<ffffffff80492a8b>] ? move_addr_to_kernel+0x2b/0x40
 [<ffffffff8049c9dc>] ? verify_iovec+0x3c/0xd0
 [<ffffffff80493bc9>] sys_sendmsg+0x189/0x320
 [<ffffffff80494807>] ? move_addr_to_user+0x67/0x80
 [<ffffffff80493015>] ? sockfd_lookup_light+0x25/0x90
 [<ffffffff80493e5f>] ? sys_sendto+0xff/0x120
 [<ffffffff80260dd1>] ? trace_hardirqs_on_caller+0xe1/0x100
 [<ffffffff805327d6>] ? trace_hardirqs_on_thunk+0x3a/0x3f
 [<ffffffff8020b9db>] system_call_fastpath+0x16/0x1b

iwl3945 0000:0c:00.0: PCI INT A disabled
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.

             reply	other threads:[~2008-08-03 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 18:35 Max Krasnyansky [this message]
2008-08-03 21:01 ` Circular locking (rtnl_mutex & _xmit_IEEE80211) during suspend David Miller

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=4895FA6F.8050209@qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox