From: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, general@lists.openfabrics.org,
Roland Dreier <rolandd@cisco.com>
Subject: Re: dst_ifdown breaks infiniband?
Date: Sun, 18 Mar 2007 22:24:44 +0200 [thread overview]
Message-ID: <20070318202444.GC11078@mellanox.co.il> (raw)
In-Reply-To: <20070318195558.GA27004@ms2.inr.ac.ru>
> Quoting Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>:
> Subject: Re: dst_ifdown breaks infiniband?
>
> Hello!
>
> > Hmm. Something I don't understand: does the code
> > in question not run on *each* device unregister?
>
> It does.
>
>
> > Why do I only see this under stress?
>
> You should have some referenced destination entries to trigger bad path.
> This should happen not only under stress.
>
> F.e. just try to ssh to something via this device. And unregister it.
> Seems, the crash is inevitable. If you do not see crash, I will be puzzled.
I did this.
What happens is:
neigh_setup is called
dst_ifdown changes the neigh->dev to loopback device
But the funny thing is that this neighbour can thinkably hang
around indefinitely now, and if it does destructor won't be called
and there won't be a crash.
To trigger a crash, I did simply
ifconfig lo down; ifconfig lo 127.0.0.1
and sure enough it crashes in drivers/infiniband/ulp/ipoib/ipoib_main.c.
--
MST
next prev parent reply other threads:[~2007-03-18 20:24 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 [this message]
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
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=20070318202444.GC11078@mellanox.co.il \
--to=mst@dev.mellanox.co.il \
--cc=general@lists.openfabrics.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rolandd@cisco.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
all inboxes | Powered by JetHome®