Bug #162

"INFO: possible recursive locking detected"

Added by Linus Lüssing about 10 years ago. Updated over 5 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Using a 3.4.0 kernel (Linux mesh-node1 3.4.0 #1 SMP PREEMPT Thu Jul 19 20:17:49 BST 2012 i686 GNU/Linux) in kvm with a few debug options and two nodes A and B connected via a single interface results in the attached traces as soon as A tries to ping B. After a 750ms lag the ICMP packets travel through fine though.
Tried batman-adv v2011.3.0, v2012.0.0 and master 3fdeaa6bfb404311b73a689e984672161403a0c2, all with the same issue (the attached traces are from the master branch).


node-A-calltrace (4.38 KB) node-A-calltrace Anonymous, 08/04/2012 03:44 PM
node-B-calltrace (4.29 KB) node-B-calltrace Anonymous, 08/04/2012 03:44 PM
lock.log (4.96 KB) lock.log Antonio Quartulli, 08/27/2012 09:28 AM



Updated by Linus Lüssing almost 10 years ago

Simon Wunderlich wrote:

This patch should fix the problem. Can you confirm?

Confirmed. Works like a charm.


Updated by Antonio Quartulli almost 10 years ago

Hello, I'm sorry but I hit this stack trace again while testing latest master...

My setup is made up by 4 VMs interconnected like a chain (node1<->node2<->node3<->node4).
I get the stack trace when I ping node 1 from a client bridged in node 2.

By the way this is strange because I remember that the bug went away while testing Simon's patch. Maybe something added later has recreated the problem? I'll try to bisect.


Updated by Linus Lüssing almost 10 years ago

Hm, just noticed that with v2012.4.0 I'm having these messages again. Were those patches (commit:b8f86c91faeb816168ecbdac0a355f316781ba77, commit:e27bb6fa916451e9eaced16e7c21d5b71a3b7f30) accidentally forgotten to be included in v2012.4.0 or were they kept back on purpose due to this issue still being reproducable in certain scenarios even with these patches?


Updated by Anonymous almost 10 years ago

These patches are non-critical and therefore were applied on top of master. As result, these patches were now sent to David and will be part of the 2012.5.0 release.


Updated by Antonio Quartulli over 9 years ago

  • Status changed from New to Resolved

Updated by Antonio Quartulli almost 9 years ago

  • Status changed from Resolved to Closed

Updated by Sven Eckelmann over 5 years ago

  • Target version set to 2013.0.0

Also available in: Atom PDF