lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 18 Mar 2007 22:24:44 +0200
From:	"Michael S. Tsirkin" <>
To:	Alexey Kuznetsov <>
Cc:	"Michael S. Tsirkin" <>,
	Linux Kernel Mailing List <>,,,
	Roland Dreier <>
Subject: Re: 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 netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists