From: Jon Paul Maloy Date: Fri, 14 Feb 2014 21:40:44 +0000 (-0500) Subject: tipc: correct usage of spin_lock() vs spin_lock_bh() X-Git-Tag: v3.15-rc1~113^2~336 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a11607f5a145818e097c64c72c839bcf6907e110;p=pandora-kernel.git tipc: correct usage of spin_lock() vs spin_lock_bh() I commit e099e86c9e24fe9aff36773600543eb31d8954d ("tipc: add node_lock protection to link lookup function") we are calling spin_lock(&node->lock) directly instead of indirectly via the tipc_node_lock(node) function. However, tipc_node_lock() is using spin_lock_bh(), not spin_lock(), something leading to unbalanced usage in one place, and a smatch warning. We fix this by consistently using tipc_node_lock()/unlock() in in the places touched by the mentioned commit. Signed-off-by: Jon Maloy Signed-off-by: David S. Miller --- Reading git-diff-tree failed