From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: vdavydov@parallels.com, netdev@vger.kernel.org
Subject: Re: Possible deadlock in ipv6?
Date: Tue, 12 Jun 2012 11:09:44 +0200 [thread overview]
Message-ID: <1339492184.22704.26.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120611.235453.953830769326224643.davem@davemloft.net>
On Mon, 2012-06-11 at 23:54 -0700, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Wed, 06 Jun 2012 17:58:34 +0200
>
> > And it seems this neigh_down() can be removed, its called later
> > (after dev->ip6_ptr is cleared)
>
> It is unclear whether we need to do the the neigh_down() in both
> the 'how' and '!how' cases. If so then we can't make this change.
>
Hmm...
Is it expected we send traffic on device dismantle ?
If no, we could do :
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index d81d026..16e0ddb 100644
--- a/net/core/neighbour.c
+++ b/net/core/neighbour.c
@@ -681,8 +681,6 @@ static int pneigh_ifdown(struct neigh_table *tbl, struct net_device *dev)
while ((n = *np) != NULL) {
if (!dev || n->dev == dev) {
*np = n->next;
- if (tbl->pdestructor)
- tbl->pdestructor(n);
if (n->dev)
dev_put(n->dev);
release_net(pneigh_net(n));
next prev parent reply other threads:[~2012-06-12 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 14:49 Possible deadlock in ipv6? Vladimir Davydov
2012-06-06 15:53 ` Eric Dumazet
2012-06-06 15:58 ` Eric Dumazet
2012-06-06 16:01 ` Vladimir Davydov
2012-06-06 17:02 ` Eric Dumazet
2012-06-12 6:54 ` David Miller
2012-06-12 9:09 ` Eric Dumazet [this message]
2012-06-21 4:05 ` 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=1339492184.22704.26.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vdavydov@parallels.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