| 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: <20110510130754.GA6667@infradead.org> Date: Tue, 10 May 2011 09:07:54 -0400 From: Christoph Hellwig <hch@...radead.org> To: KY Srinivasan <kys@...rosoft.com> Cc: Christoph Hellwig <hch@...radead.org>, Greg KH <greg@...ah.com>, "gregkh@...e.de" <gregkh@...e.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>, "virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org> Subject: Re: various vmbus review comments > I must be missing something here. As I look at the block driver (and > this is indicative of other drivers as well); the exit routine - > blkvsc_drv_exit, first iterates through all the devices it manages > and invokes device_unregister() on each of the devices and then > invokes vmbus_child_driver_unregister() which is just a wrapper on > driver_unregister(). So, if I understand you correctly, you want the devices to > persist even if there is no driver bound to them. So, if I eliminated the code > that iterates over the devices and unregisters them, that should fix the problem > and I can do this without changing the vmbus core interfaces. If that actually works go for it. But there's no way to know that without actually implementing and testing it. -- 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