| 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: <d120d5000703090934r45c39f74l2a51eda986b1f07b@mail.gmail.com> Date: Fri, 9 Mar 2007 12:34:38 -0500 From: "Dmitry Torokhov" <dmitry.torokhov@...il.com> To: "Oliver Neukum" <oneukum@...e.de> Cc: "Alan Stern" <stern@...land.harvard.edu>, "Maneesh Soni" <maneesh@...ibm.com>, gregkh@...e.de, linux-kernel@...r.kernel.org Subject: Re: refcounting drivers' data structures used in sysfs buffers On 3/9/07, Oliver Neukum <oneukum@...e.de> wrote: > Am Freitag, 9. März 2007 18:02 schrieb Dmitry Torokhov: > > > I think we already have all refcounting that is needed. What is > > missing is subsystem-provided ->release() hooks for drivers to release > > driver-specific resources when a device finally goes away. > > This is an interesting idea. Is it nice to pass through release() > but not open() ? > Not sure if I follow... Generally speaking open is not a mandatory operation; however every object in driver model has a release method. What I am saying is that certain drivers need to have their disconnect method split in 2 parts - one that shuts down the device and second is releases resources that might be accesses through sysfs (and other kernel parts). That second part will have to be called from subsystem's core ->release() method se we need a release() hook. -- Dmitry - 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