From: Jarek Poplawski <jarkao2@o2.pl>
To: Simon Arlott <simon@arlott.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sridhar Samudrala <sri@us.ibm.com>,
netdev@vger.kernel.org, lksctp-developers@lists.sourceforge.net
Subject: [PATCH][SCTP] Re: lockdep: inconsistent lock state ipv6_add_addr/sctp_v6_copy_addrlist (2.6.21-rc1)
Date: Thu, 8 Mar 2007 08:47:51 +0100 [thread overview]
Message-ID: <20070308074751.GA2085@ff.dom.local> (raw)
In-Reply-To: <45E15215.4070600@simon.arlott.org.uk>
On 25-02-2007 10:08, Simon Arlott wrote:
> This happens on every boot if more information is needed:
>
> [ 37.393715] =================================
> [ 37.393830] [ INFO: inconsistent lock state ]
> [ 37.393881] 2.6.21-rc1-git #146
> [ 37.393929] ---------------------------------
> [ 37.393979] inconsistent {softirq-on-R} -> {in-softirq-W} usage.
> [ 37.394040] hotplug/1072 [HC0[0]:SC1[2]:HE1:SE0] takes:
> [ 37.394092] (&ndev->lock){-+-?}, at: [<b04a7944>] ipv6_add_addr+0x164/0x1e0
> [ 37.394308] {softirq-on-R} state was registered at:
> [ 37.394359] [<b013fc42>] __lock_acquire+0x622/0xbb0
> [ 37.394515] [<b0140652>] lock_acquire+0x62/0x80
> [ 37.394678] [<b0511c65>] _read_lock+0x35/0x50
> [ 37.394834] [<b050e200>] sctp_v6_copy_addrlist+0x30/0xc0
...
[SCTP] ipv6: inconsistent lock state ipv6_add_addr/sctp_v6_copy_addrlist
lockdep found that dev->lock taken from softirq in ipv6_add_addr
is also taken in sctp_v6_copy_addrlist with softirqs enabled, so
lockup is possible.
Noticed-by: Simon Arlott <simon@arlott.org>
Signed-off-by: Jarek Poplawski <jarkao2@o2.pl>
---
diff -Nurp linux-2.6.21-rc2-mm2-/net/sctp/ipv6.c linux-2.6.21-rc2-mm2/net/sctp/ipv6.c
--- linux-2.6.21-rc2-mm2-/net/sctp/ipv6.c 2007-02-21 19:46:49.000000000 +0100
+++ linux-2.6.21-rc2-mm2/net/sctp/ipv6.c 2007-03-07 21:57:37.000000000 +0100
@@ -360,7 +360,7 @@ static void sctp_v6_copy_addrlist(struct
return;
}
- read_lock(&in6_dev->lock);
+ read_lock_bh(&in6_dev->lock);
for (ifp = in6_dev->addr_list; ifp; ifp = ifp->if_next) {
/* Add the address to the local list. */
addr = t_new(struct sctp_sockaddr_entry, GFP_ATOMIC);
@@ -374,7 +374,7 @@ static void sctp_v6_copy_addrlist(struct
}
}
- read_unlock(&in6_dev->lock);
+ read_unlock_bh(&in6_dev->lock);
rcu_read_unlock();
}
next parent reply other threads:[~2007-03-08 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45E15215.4070600@simon.arlott.org.uk>
2007-03-08 7:47 ` Jarek Poplawski [this message]
2007-03-08 11:00 ` [PATCH][SCTP] Re: lockdep: inconsistent lock state ipv6_add_addr/sctp_v6_copy_addrlist (2.6.21-rc1) Herbert Xu
2007-03-08 11:02 ` Herbert Xu
2007-03-08 11:15 ` Jarek Poplawski
2007-03-08 22:44 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070308074751.GA2085@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=simon@arlott.org \
--cc=sri@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).