| 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: <20070413152453.571e887a@gondolin.boeblingen.de.ibm.com> Date: Fri, 13 Apr 2007 15:24:53 +0200 From: Cornelia Huck <cornelia.huck@...ibm.com> To: "Markus Rechberger" <markus.rechberger@....com> Cc: "Alan Stern" <stern@...land.harvard.edu>, "USB development list" <linux-usb-devel@...ts.sourceforge.net>, "Kernel development list" <linux-kernel@...r.kernel.org> Subject: Re: How should an exit routine wait for release() callbacks? On Fri, 13 Apr 2007 13:42:04 +0200, "Markus Rechberger" <markus.rechberger@....com> wrote: > seems like you have the same problem as the dvb framework has/had. > > http://mcentral.de/hg/~mrec/v4l-dvb-stable > > The last 3 changesets do the trick to not oops, it will delay the > deinitialization of the device till the last user closed the device node. Probably dumb question (since I'm not at all familiar with the dvb code): Isn't that a different race you're solving there? I don't see any driver core objects involved (except class devices created by class_device_create, which obviously don't have the release function problem). This looks more like a race of "we want an object to go away, but a user still has a file open" (which would be similar to the kobject<->sysfs lifetime rules issues, where work is currently ongoing). - 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