linux-kernel - Re: latest 3.14.0-rc8+ : "INFO: inconsistent lock state "

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-prev] [day] [month] [year] [list]

Date:	Fri, 28 Mar 2014 21:23:17 -0700
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	jongman.heo@...sung.com
Cc:	linux-net@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Hannes Frederic Sowa <hannes@...essinduktion.org>
Subject: Re: latest 3.14.0-rc8+ : "INFO: inconsistent lock state "

On Fri, Mar 28, 2014 at 8:21 PM, Jongman Heo <jongman.heo@...sung.com> wrote:
>
> Hi, guys,
>
> With today's linus git tree, I got following messages;
>
> [   97.426196] =================================
> [   97.426198] [ INFO: inconsistent lock state ]
> [   97.426221] 3.14.0-rc8+ #45 Tainted: G        W
> [   97.426224] ---------------------------------
> [   97.426227] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
> [   97.426229] kworker/7:1/101 [HC0[0]:SC0[0]:HE1:SE1] takes:
> [   97.426231]  (&addrconf_stats->syncp.seq){+.?...}, at: [<c0ac9c81>] mld_send_initial_cr.part.30+0x81/0xa0
> [   97.426255] {IN-SOFTIRQ-W} state was registered at:
> [   97.426258]   [<c04a8514>] __lock_acquire+0x414/0x18e0
> [   97.426265]   [<c04a9a78>] lock_acquire+0x98/0x120
> [   97.426268]   [<c0ac91cf>] mld_sendpack+0xdf/0x5b0
> [   97.426270]   [<c0acaaf1>] mld_ifc_timer_expire+0x191/0x2c0
> [   97.426272]   [<c0465a35>] call_timer_fn+0x75/0x160
> [   97.426276]   [<c0466762>] run_timer_softirq+0x192/0x230
> [   97.426281]   [<c045fcbb>] __do_softirq+0xfb/0x2b0
> [   97.426286] irq event stamp: 33365
> [   97.426289] hardirqs last  enabled at (33365): [<c045ffcb>] __local_bh_enable_ip+0x6b/0xc0
> [   97.426292] hardirqs last disabled at (33363): [<c045fd05>] __do_softirq+0x145/0x2b0
> [   97.426294] softirqs last  enabled at (33364): [<c045fd64>] __do_softirq+0x1a4/0x2b0
> [   97.426297] softirqs last disabled at (33341): [<c0414335>] do_softirq_own_stack+0x35/0x40
> [   97.426303]
> other info that might help us debug this:
> [   97.426305]  Possible unsafe locking scenario:
>
> [   97.426306]        CPU0
> [   97.426307]        ----
> [   97.426308]   lock(&addrconf_stats->syncp.seq);
> [   97.426310]   <Interrupt>
> [   97.426311]     lock(&addrconf_stats->syncp.seq);
> [   97.426313]
>  *** DEADLOCK ***

Does the following patch help?

diff --git a/net/ipv6/mcast.c b/net/ipv6/mcast.c
index e1e4735..74a774a 100644
--- a/net/ipv6/mcast.c
+++ b/net/ipv6/mcast.c
@@ -1588,7 +1588,7 @@ static void mld_sendpack(struct sk_buff *skb)

        rcu_read_lock();
        idev = __in6_dev_get(skb->dev);
-       IP6_UPD_PO_STATS(net, idev, IPSTATS_MIB_OUT, skb->len);
+       IP6_UPD_PO_STATS_BH(net, idev, IPSTATS_MIB_OUT, skb->len);

        payload_len = (skb_tail_pointer(skb) - skb_network_header(skb)) -
                sizeof(*pip6);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/