netdev - [request for stable inclusion] tipc: fix lockdep warning during bearer initialization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Aug 2013 11:23:08 +0800
From:	wangweidong <wangweidong1@...wei.com>
To:	<davem@...emloft.net>
CC:	<netdev@...r.kernel.org>, <stable@...r.kernel.org>,
	<ying.xue@...driver.com>, <jon.maloy@...csson.com>,
	<paul.gortmaker@...driver.com>, <dingtianhong@...wei.com>,
	Li Zefan <lizefan@...wei.com>
Subject: [request for stable inclusion] tipc: fix lockdep warning during bearer
 initialization

Hi Ying Xue, Jon, Paul or David,

4225a398c1352a7a5c14dc07277cb5cc4473983b
tipc: fix lockdep warning during bearer initialization

This looks applicable to stable-3.0/3.2/3.4, that fixed one deadlock. 
With the tipc-config cmd, I can reproduce that. The deadlock possibly
occur when the second TIPC bearer is registered, the deadlock can perhaps
really happen. And this patch works well. But git am or patch -p1 failed,
because a previous patch [commit 617d3c7a5 (tipc: compress out gratuitous
extra carriage returns)] deletes some blank lines. With some modifies, it
was built successful for me. What do you think?

And the bug was fixed in 3.7; The commit got its way into mainline in 3.7
cycle.

Thanks!
Wang Weidong

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html