From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org
Subject: [RFT] proxy arp deadlock possible
Date: Wed, 4 Apr 2007 15:26:35 -0700 [thread overview]
Message-ID: <20070404152635.7c3ba33e@localhost> (raw)
In-Reply-To: <20070404213050.GA19261@redhat.com>
Thanks Dave, there is a classic AB BA deadlock here.
We should break the dependency like this.
Could someone who uses proxy ARP test this?
-----
Need to drop one of the locks to avoid deadlock between
proxy arp and incoming arp receive.
---
net/core/neighbour.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index cfc6001..d6b3a62 100644
--- a/net/core/neighbour.c
+++ b/net/core/neighbour.c
@@ -1212,6 +1212,7 @@ static void neigh_proxy_process(unsigned
unsigned long now = jiffies;
struct sk_buff *skb;
+rescan:
spin_lock(&tbl->proxy_queue.lock);
skb = tbl->proxy_queue.next;
@@ -1224,13 +1225,20 @@ static void neigh_proxy_process(unsigned
if (tdif <= 0) {
struct net_device *dev = back->dev;
__skb_unlink(back, &tbl->proxy_queue);
+
+ /* drop lock to avoid deadlock */
+ spin_unlock(&tbl->proxy_queue.lock);
+
if (tbl->proxy_redo && netif_running(dev))
tbl->proxy_redo(back);
else
kfree_skb(back);
dev_put(dev);
- } else if (!sched_next || tdif < sched_next)
+ goto rescan;
+ }
+
+ if (!sched_next || tdif < sched_next)
sched_next = tdif;
}
del_timer(&tbl->proxy_timer);
--
1.4.1
next prev parent reply other threads:[~2007-04-04 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 21:30 lockdep report from 2.6.20.5-rc1 Dave Jones
2007-04-04 22:26 ` Stephen Hemminger [this message]
2007-04-05 0:44 ` [RFT] proxy arp deadlock possible Herbert Xu
2007-04-05 1:10 ` Arjan van de Ven
2007-04-05 4:49 ` Dave Jones
2007-04-05 5:32 ` Herbert Xu
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=20070404152635.7c3ba33e@localhost \
--to=shemminger@linux-foundation.org \
--cc=davej@redhat.com \
--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).