From: Ingo Molnar <mingo@elte.hu>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: [lock validator] inet6_destroy_sock(): soft-safe -> soft-unsafe lock dependency
Date: Thu, 2 Feb 2006 11:54:29 +0100 [thread overview]
Message-ID: <20060202105429.GA4895@elte.hu> (raw)
In-Reply-To: <20060202084824.GA17299@gondor.apana.org.au>
hm, i got a new one:
============================================
[ BUG: circular locking deadlock detected! ]
--------------------------------------------
sshd/28997 is trying to acquire lock:
(&sk->sk_lock.slock){-+}, at: [<c0c6be28>] packet_rcv+0xbf/0x34b
but task is already holding lock:
(&dev->xmit_lock){-+}, at: [<c0bb04ec>] qdisc_restart+0x46/0x207
which lock already depends on the new lock,
which could lead to circular deadlocks!
the dependency chain (in reverse order) is:
-> #2 (&dev->xmit_lock){-+}: [<c0bb04ec>] qdisc_restart+0x46/0x207
-> #1 (&dev->queue_lock){-+}: [<c0b98137>] dev_queue_xmit+0xc3/0x21e
-> #0 (&sk->sk_lock.slock){-+}: [<c0c6be28>] packet_rcv+0xbf/0x34b
other info that might help us debug this:
1 locks held by sshd/28997:
#0: (&dev->xmit_lock){-+}, at: [<c0bb04ec>] qdisc_restart+0x46/0x207
stack backtrace:
[<c0103ecd>] show_trace+0xd/0xf
[<c0103ee4>] dump_stack+0x15/0x17
[<c014019e>] print_circular_bug_tail+0x42/0x4b
[<c0141716>] debug_lock_chain+0xb30/0xd58
[<c014196f>] debug_lock_chain_spin+0x31/0x48
[<c0415b8c>] _raw_spin_lock+0x34/0x7f
[<c0d3c12d>] _spin_lock+0x8/0xa
[<c0c6be28>] packet_rcv+0xbf/0x34b
[<c0b98052>] dev_queue_xmit_nit+0xbb/0xdd
[<c0bb05a5>] qdisc_restart+0xff/0x207
[<c0b9814e>] dev_queue_xmit+0xda/0x21e
[<c0bde286>] ip_output+0x237/0x2c1
[<c0bdd9a4>] ip_queue_xmit+0x394/0x417
[<c0beafb7>] tcp_transmit_skb+0x5d4/0x5f6
[<c0beca28>] __tcp_push_pending_frames+0x256/0x305
[<c0be43f1>] tcp_sendmsg+0x8ae/0x975
[<c0bfabd3>] inet_sendmsg+0x39/0x46
[<c0b8fd44>] do_sock_write+0xbd/0xc6
[<c0b8fe7b>] sock_aio_write+0x56/0x64
[<c016c922>] do_sync_write+0xb1/0xe6
[<c016cd71>] vfs_write+0xbd/0x155
[<c016d5db>] sys_write+0x3b/0x60
[<c0102c39>] syscall_call+0x7/0xb
next prev parent reply other threads:[~2006-02-02 10:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 0:18 [lock validator] net/ipv4/fib_hash.c: illegal {enabled-softirqs} -> {used-in-softirq} usage? Ingo Molnar
2006-01-27 1:41 ` Herbert Xu
2006-01-28 15:22 ` [lock validator] inet6_destroy_sock(): soft-safe -> soft-unsafe lock dependency Ingo Molnar
2006-01-28 15:44 ` Ingo Molnar
2006-01-31 10:27 ` Herbert Xu
2006-01-31 10:43 ` David S. Miller
2006-01-31 11:21 ` Ingo Molnar
2006-02-01 13:32 ` Ingo Molnar
2006-02-01 20:26 ` Herbert Xu
2006-02-02 7:46 ` Ingo Molnar
2006-02-02 8:48 ` Herbert Xu
2006-02-02 9:04 ` David S. Miller
2006-02-02 10:54 ` Ingo Molnar [this message]
2006-02-02 11:27 ` Ingo Molnar
2006-02-02 12:19 ` Herbert Xu
2006-02-02 12:17 ` Herbert Xu
2006-02-02 13:54 ` Ingo Molnar
2006-01-31 21:24 ` Ingo Molnar
2006-01-31 22:06 ` Herbert Xu
2006-02-01 10:42 ` Herbert Xu
2006-02-01 11:13 ` Ingo Molnar
2006-02-03 1:01 ` David S. 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=20060202105429.GA4895@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).