From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: linux-kernel@vger.kernel.org
Subject: possible recursive locking, 2.6.24-rc7
Date: Sun, 13 Jan 2008 17:51:42 +0200 [thread overview]
Message-ID: <20080113155142.M6056@visp.net.lb> (raw)
Hi, got in dmesg
Not sure where to send (there is TCP), so sending netdev@ and kernel@
[159859.491752]
[159859.491755] =============================================
[159859.492021] [ INFO: possible recursive locking detected ]
[159859.492156] 2.6.24-rc7-devel #2
[159859.492284] ---------------------------------------------
[159859.492418] swapper/0 is trying to acquire lock:
[159859.492550] (&q->lock){++..}, at: [<c01175ff>] __wake_up+0x15/0x42
[159859.492883]
[159859.492884] but task is already holding lock:
[159859.493140] (&q->lock){++..}, at: [<c01175ff>] __wake_up+0x15/0x42
[159859.493466]
[159859.493467] other info that might help us debug this:
[159859.493726] 5 locks held by swapper/0:
[159859.495687] #0: (rcu_read_lock){..--}, at: [<c02dd9af>]
netif_receive_skb+
0x9c/0x3a7
[159859.496141] #1: (rcu_read_lock){..--}, at: [<c02f8072>]
ip_local_deliver_f
inish+0x30/0x18d
[159859.496604] #2: (slock-AF_INET/1){-+..}, at: [<c0310474>]
tcp_v4_rcv+0x426
/0x812
[159859.497104] #3: (clock-AF_INET){-.-?}, at: [<c02d7684>]
sock_def_readable+
0x18/0x6e
[159859.497555] #4: (&q->lock){++..}, at: [<c01175ff>] __wake_up+0x15/0x42
[159859.497931]
[159859.497932] stack backtrace:
[159859.498185] Pid: 0, comm: swapper Not tainted 2.6.24-rc7-devel #2
[159859.498320] [<c0105e68>] show_trace_log_lvl+0x1a/0x2f
[159859.498505] [<c0106810>] show_trace+0x12/0x14
[159859.498690] [<c0107107>] dump_stack+0x6c/0x72
[159859.498872] [<c01384c0>] __lock_acquire+0x172/0xb8c
[159859.499057] [<c01392a7>] lock_acquire+0x5f/0x78
[159859.499239] [<c03299cf>] _spin_lock_irqsave+0x34/0x44
[159859.499423] [<c01175ff>] __wake_up+0x15/0x42
[159859.499604] [<c01869ea>] ep_poll_safewake+0x8e/0xbf
[159859.499787] [<c01876b3>] ep_poll_callback+0x9f/0xac
[159859.499970] [<c0115d36>] __wake_up_common+0x32/0x5c
[159859.500154] [<c011761b>] __wake_up+0x31/0x42
[159859.500335] [<c02d76ae>] sock_def_readable+0x42/0x6e
[159859.500518] [<c0309105>] tcp_rcv_established+0x3bc/0x643
[159859.500704] [<c030e588>] tcp_v4_do_rcv+0x2f/0x325
[159859.500887] [<c0310817>] tcp_v4_rcv+0x7c9/0x812
[159859.501069] [<c02f8149>] ip_local_deliver_finish+0x107/0x18d
[159859.501255] [<c02f854e>] ip_local_deliver+0x72/0x7c
[159859.501438] [<c02f8023>] ip_rcv_finish+0x2cf/0x2ee
[159859.501623] [<c02f84b2>] ip_rcv+0x211/0x23b
[159859.501805] [<c02ddc63>] netif_receive_skb+0x350/0x3a7
[159859.501989] [<f88f2b6d>] bnx2_poll+0x975/0xb45 [bnx2]
[159859.502177] [<c02dfdab>] net_rx_action+0x6c/0x116
[159859.502360] [<c0120ed8>] __do_softirq+0x6f/0xe9
[159859.502543] [<c0120f8c>] do_softirq+0x3a/0x52
[159859.502728] [<c012128b>] irq_exit+0x47/0x7b
[159859.502911] [<c01076af>] do_IRQ+0x81/0x96
[159859.503098] [<c010586a>] common_interrupt+0x2e/0x34
[159859.503288] [<c0103434>] mwait_idle+0x12/0x14
[159859.503476] [<c010353d>] cpu_idle+0x7b/0x95
[159859.503662] [<c03272c9>] rest_init+0x49/0x4b
[159859.503844] [<c0449c08>] start_kernel+0x2f9/0x301
[159859.504030] [<00000000>] 0x0
[159859.504210] =======================
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next reply other threads:[~2008-01-13 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 15:51 Denys Fedoryshchenko [this message]
2008-01-13 16:22 ` possible recursive locking, 2.6.24-rc7 Peter Zijlstra
2008-01-13 18:44 ` Peter Zijlstra
2008-01-13 19:25 ` Denys Fedoryshchenko
2008-01-14 18:15 ` Stefan Richter
-- strict thread matches above, loose matches on Subject: below --
2008-01-13 15:48 Denys Fedoryshchenko
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=20080113155142.M6056@visp.net.lb \
--to=denys@visp.net.lb \
--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 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.