| lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20070318223653.GO11078@mellanox.co.il> Date: Mon, 19 Mar 2007 00:36:53 +0200 From: "Michael S. Tsirkin" <mst@....mellanox.co.il> To: "Eric W. Biederman" <ebiederman@...i.com> Cc: "Michael S. Tsirkin" <mst@....mellanox.co.il>, Alexey Kuznetsov <kuznet@....inr.ac.ru>, netdev@...r.kernel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, general@...ts.openfabrics.org Subject: Re: [ofa-general] Re: dst_ifdown breaks infiniband? > Quoting Eric W. Biederman <ebiederman@...i.com>: > Subject: Re: [ofa-general] Re: dst_ifdown breaks infiniband? > > "Michael S. Tsirkin" <mst@....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. -- MST - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists