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
| ||
|
Date: Wed, 18 Apr 2007 10:11:17 +0200 From: Cornelia Huck <cornelia.huck@...ibm.com> To: Tejun Heo <htejun@...il.com> Cc: linux-kernel <linux-kernel@...r.kernel.org>, Alan Stern <stern@...land.harvard.edu>, Greg K-H <greg@...ah.com>, Rusty Russell <rusty@...tcorp.com.au>, dmitry.torokhov@...il.com Subject: Re: [PATCH RFD] alternative kobject release wait mechanism On Wed, 18 Apr 2007 03:49:01 +0900, Tejun Heo <htejun@...il.com> wrote: > Oh, one more thing, with proper code audit, we can just make > device_unregister() do the waiting instead of adding separate > device_unregister_wait(). I think that will be a good step toward > immediate-detach driver model. Do we really want that? If the release function doesn't sit in the module, or if the device_unregister() is done for other reasons in a non-module, we don't care about lingering references. There's no need to wait (and possibly lock up) there. - 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