[lkml]   [2007]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dst_ifdown breaks infiniband?
> Quoting Alexey Kuznetsov <>:
> 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

and sure enough it crashes in drivers/infiniband/ulp/ipoib/ipoib_main.c.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-03-18 21:27    [W:0.122 / U:3.624 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site