Skip to contentSkip to conversation

2.6.18 -- INFO: possible recursive locking detected

DISCUSSION Miles Lane 2 participants 2 messages Sep 21, 2006 – Sep 22, 2006

lore
Share & tools
lore

Miles Lane

author
#0 lore raw

=============================================
[ INFO: possible recursive locking detected ]
---------------------------------------------
knodemgrd_1/13913 is trying to acquire lock:
(&s->rwsem){..--}, at: [<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394]

but task is already holding lock:
(&s->rwsem){..--}, at: [<f89610d8>] nodemgr_host_thread+0x739/0x8a7 [ieee1394]

other info that might help us debug this:
1 lock held by knodemgrd_1/13913:
#0: (&s->rwsem){..--}, at: [<f89610d8>]

nodemgr_host_thread+0x739/0x8a7 [ieee1394]

stack backtrace:
[<c1003ef5>] show_trace_log_lvl+0x58/0x16a
[<c100506d>] show_trace+0xd/0x10
[<c1005087>] dump_stack+0x17/0x1c
[<c102e485>] __lock_acquire+0x79b/0x9ef
[<c102e9b6>] lock_acquire+0x5e/0x80
[<c102b73e>] down_read+0x28/0x3a
[<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394]
[<f89610f7>] nodemgr_host_thread+0x758/0x8a7 [ieee1394]
[<c1001005>] kernel_thread_helper+0x5/0xb
DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb
Leftover inexact backtrace:
[<c100506d>] show_trace+0xd/0x10
[<c1005087>] dump_stack+0x17/0x1c
[<c102e485>] __lock_acquire+0x79b/0x9ef
[<c102e9b6>] lock_acquire+0x5e/0x80
[<c102b73e>] down_read+0x28/0x3a
[<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394]
[<f89610f7>] nodemgr_host_thread+0x758/0x8a7 [ieee1394]
[<c1001005>] kernel_thread_helper+0x5/0xb

ieee1394: send packet at S400: ffc0a140 ffc1ffff f0000234

#1 lore raw
Quoted 8 lines · Miles Lane

=============================================
[ INFO: possible recursive locking detected ]
---------------------------------------------
knodemgrd_1/13913 is trying to acquire lock:
(&s->rwsem){..--}, at: [<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394]

but task is already holding lock:
(&s->rwsem){..--}, at: [<f89610d8>] nodemgr_host_thread+0x739/0x8a7 [ieee1394]

Thanks for the report.

There is already a fix in -mm and linux1394-2.6.git which will presumably appear in 2.6.19-rc1.
http://kernel.org/git/?p=linux/kernel/git/ieee1394/linux1394-2.6.git;a=commitdiff_plain;h=9b516010863195ba7db061233a3eeffe779130e8

To verify the fix, you can probably apply this patch as-is to Linux 2.6.18. Alternatively you can get it with this patchset:
http://me.in-berlin.de/~s5r6/linux1394/updates/2.6.18-rc6/
(You need v159 or later to get the recursive locking fix. I will ready a patchset against 2.6.18 soon but I expect it to be the same as against 2.6.18-rc6.)

Quoted 27 lines

other info that might help us debug this:
1 lock held by knodemgrd_1/13913:
#0: (&s->rwsem){..--}, at: [<f89610d8>]

nodemgr_host_thread+0x739/0x8a7 [ieee1394]

stack backtrace:
 [<c1003ef5>] show_trace_log_lvl+0x58/0x16a
 [<c100506d>] show_trace+0xd/0x10
 [<c1005087>] dump_stack+0x17/0x1c
 [<c102e485>] __lock_acquire+0x79b/0x9ef
 [<c102e9b6>] lock_acquire+0x5e/0x80
 [<c102b73e>] down_read+0x28/0x3a
 [<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394]
 [<f89610f7>] nodemgr_host_thread+0x758/0x8a7 [ieee1394]
 [<c1001005>] kernel_thread_helper+0x5/0xb
DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb
Leftover inexact backtrace:
 [<c100506d>] show_trace+0xd/0x10
 [<c1005087>] dump_stack+0x17/0x1c
 [<c102e485>] __lock_acquire+0x79b/0x9ef
 [<c102e9b6>] lock_acquire+0x5e/0x80
 [<c102b73e>] down_read+0x28/0x3a
 [<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394]
 [<f89610f7>] nodemgr_host_thread+0x758/0x8a7 [ieee1394]
 [<c1001005>] kernel_thread_helper+0x5/0xb

ieee1394: send packet at S400: ffc0a140 ffc1ffff f0000234 -

Signature · 3 lines
Stefan Richter
-=====-=-==- =--= =--==
http://arcgraph.de/sr/