From: Cong Wang <amwang@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>, Cong Wang <amwang@redhat.com>
Subject: [PATCH net-next v12 05/11] ipv6: do not call ndisc_send_rs() with write lock
Date: Sat, 31 Aug 2013 13:44:32 +0800 [thread overview]
Message-ID: <1377927878-23975-6-git-send-email-amwang@redhat.com> (raw)
In-Reply-To: <1377927878-23975-1-git-send-email-amwang@redhat.com>
From: Cong Wang <amwang@redhat.com>
Because vxlan module will call ip6_dst_lookup() in TX path,
which will hold write lock. So we have to release this write lock
before calling ndisc_send_rs(), otherwise could deadlock.
Reviewed-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: Cong Wang <amwang@redhat.com>
---
net/ipv6/addrconf.c | 10 +++++++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index 6194513..baaaead 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -3090,6 +3090,7 @@ static int addrconf_ifdown(struct net_device *dev, int how)
static void addrconf_rs_timer(unsigned long data)
{
struct inet6_dev *idev = (struct inet6_dev *)data;
+ struct net_device *dev = idev->dev;
struct in6_addr lladdr;
write_lock(&idev->lock);
@@ -3104,12 +3105,14 @@ static void addrconf_rs_timer(unsigned long data)
goto out;
if (idev->rs_probes++ < idev->cnf.rtr_solicits) {
- if (!__ipv6_get_lladdr(idev, &lladdr, IFA_F_TENTATIVE))
- ndisc_send_rs(idev->dev, &lladdr,
+ write_unlock(&idev->lock);
+ if (!ipv6_get_lladdr(dev, &lladdr, IFA_F_TENTATIVE))
+ ndisc_send_rs(dev, &lladdr,
&in6addr_linklocal_allrouters);
else
- goto out;
+ goto put;
+ write_lock(&idev->lock);
/* The wait after the last probe can be shorter */
addrconf_mod_rs_timer(idev, (idev->rs_probes ==
idev->cnf.rtr_solicits) ?
@@ -3125,6 +3128,7 @@ static void addrconf_rs_timer(unsigned long data)
out:
write_unlock(&idev->lock);
+put:
in6_dev_put(idev);
}
--
1.7.7.6
next prev parent reply other threads:[~2013-08-31 5:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 5:44 [PATCH net-next v12 00/11] vxlan: add ipv6 support Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 01/11] ipv6: move ip6_dst_hoplimit() into core kernel Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 02/11] ipv6: move ip6_local_out " Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 03/11] ipv6: export a stub for IPv6 symbols used by vxlan Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 04/11] ipv6: export in6addr_loopback to modules Cong Wang
2013-08-31 5:44 ` Cong Wang [this message]
2013-08-31 5:44 ` [PATCH net-next v12 06/11] vxlan: add ipv6 support Cong Wang
2013-08-31 17:27 ` Stephen Hemminger
2013-09-02 1:17 ` Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 07/11] vxlan: add ipv6 route short circuit support Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 08/11] ipv6: move in6_dev_finish_destroy() into core kernel Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 09/11] vxlan: add ipv6 proxy support Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 10/11] ipv6: Add generic UDP Tunnel segmentation Cong Wang
2013-08-31 5:44 ` [PATCH net-next v12 11/11] net: unify skb_udp_tunnel_segment() and skb_udp6_tunnel_segment() Cong Wang
2013-09-01 2:30 ` [PATCH net-next v12 00/11] vxlan: add ipv6 support 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=1377927878-23975-6-git-send-email-amwang@redhat.com \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).