From: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
To: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
Cc: "Eric W. Biederman" <ebiederman@lnxi.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
general@lists.openfabrics.org
Subject: Re: [ofa-general] Re: dst_ifdown breaks infiniband?
Date: Mon, 19 Mar 2007 00:42:34 +0200 [thread overview]
Message-ID: <20070318224234.GP11078@mellanox.co.il> (raw)
In-Reply-To: <20070318223653.GO11078@mellanox.co.il>
> Quoting Michael S. Tsirkin <mst@dev.mellanox.co.il>:
> Subject: Re: [ofa-general] Re: dst_ifdown breaks infiniband?
>
> > Quoting Eric W. Biederman <ebiederman@lnxi.com>:
> > Subject: Re: [ofa-general] Re: dst_ifdown breaks infiniband?
> >
> > "Michael S. Tsirkin" <mst@dev.mellanox.co.il> writes:
> >
> > >> > Why is neighbour->dev changed here?
> > >>
> > >> It holds reference to device and prevents its destruction.
> > >> If dst is held somewhere, we cannot destroy the device and deadlock
> > >> while unregister.
> > >
> > > BTW, can this ever happen for the loopback device itself?
> > > Is it ever unregistered?
> >
> > Well I don't think the loopback device is currently but as soon
> > as we get network namespace support we will have multiple loopback
> > devices and they will get unregistered when we remove the network
> > namespace.
>
> Hmm. Then the code moving dst->dev to point to the loopback
> device will have to be fixed too. I'll post a patch a bit later.
Does this look sane (untested)?
Signed-off-by: Michael S. Tsirkin <mst@dev.mellanox.co.il>
diff --git a/net/core/dst.c b/net/core/dst.c
index 764bccb..8283158 100644
--- a/net/core/dst.c
+++ b/net/core/dst.c
@@ -235,6 +236,8 @@ again:
static inline void dst_ifdown(struct dst_entry *dst, struct net_device *dev,
int unregister)
{
+ struct neighbour *neigh;
+
if (dst->ops->ifdown)
dst->ops->ifdown(dst, dev, unregister);
@@ -245,14 +248,13 @@ static inline void dst_ifdown(struct dst_entry *dst, struct net_device *dev,
dst->input = dst_discard_in;
dst->output = dst_discard_out;
} else {
- dst->dev = &loopback_dev;
- dev_hold(&loopback_dev);
- dev_put(dev);
- if (dst->neighbour && dst->neighbour->dev == dev) {
- dst->neighbour->dev = &loopback_dev;
- dev_put(dev);
- dev_hold(&loopback_dev);
+ neigh = dst->neighbour;
+ if (neigh && neigh->dev == dev) {
+ dst->neighbour = NULL;
+ neigh_release(neigh);
}
+ dst->dev = NULL;
+ dev_put(dev);
}
}
--
MST
next prev parent reply other threads:[~2007-03-18 22:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 15:55 Michael S. Tsirkin
2007-03-18 19:12 ` Alexey Kuznetsov
2007-03-18 19:46 ` Michael S. Tsirkin
2007-03-18 19:55 ` Alexey Kuznetsov
2007-03-18 20:24 ` Michael S. Tsirkin
2007-03-18 19:53 ` Michael S. Tsirkin
2007-03-18 20:18 ` Alexey Kuznetsov
2007-03-18 20:29 ` Michael S. Tsirkin
2007-03-19 9:36 ` Michael S. Tsirkin
2007-03-19 9:55 ` Michael S. Tsirkin
2007-03-19 12:05 ` Alexey Kuznetsov
2007-03-19 12:12 ` Michael S. Tsirkin
2007-03-19 12:59 ` Alexey Kuznetsov
2007-03-19 15:13 ` Michael S. Tsirkin
2007-03-19 23:20 ` Alexey Kuznetsov
2007-03-20 16:02 ` Michael S. Tsirkin
2007-03-20 23:34 ` David Miller
2007-03-19 12:13 ` Michael S. Tsirkin
2007-03-18 20:25 ` Michael S. Tsirkin
2007-03-18 22:24 ` [ofa-general] " Eric W. Biederman
2007-03-18 22:36 ` Michael S. Tsirkin
2007-03-18 22:42 ` Michael S. Tsirkin [this message]
2007-03-19 0:13 ` David Miller
2007-03-19 5:19 ` Michael S. Tsirkin
2007-03-19 5:30 ` Eric W. Biederman
2007-03-19 6:13 ` David Miller
2007-03-19 9:34 ` Alexey Kuznetsov
2007-03-19 15:10 ` Eric W. Biederman
2007-03-19 9:24 ` Alexey Kuznetsov
2007-03-19 9:33 ` Michael S. Tsirkin
2007-03-19 9:20 ` Alexey Kuznetsov
2007-03-18 20:33 ` Michael S. Tsirkin
2007-03-18 21:06 ` Michael S. Tsirkin
2007-03-18 21:20 ` Michael S. Tsirkin
2007-03-19 5:15 ` Michael S. Tsirkin
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=20070318224234.GP11078@mellanox.co.il \
--to=mst@dev.mellanox.co.il \
--cc=ebiederman@lnxi.com \
--cc=general@lists.openfabrics.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®