| 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, 7 Mar 2007 17:59:28 +0100 From: Oliver Neukum <oliver@...kum.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, Hugh Dickins <hugh@...itas.com>, Oliver Neukum <oliver@...kum.name>, Maneesh Soni <maneesh@...ibm.com>, Greg Kroah-Hartman <gregkh@...e.de>, Adrian Bunk <bunk@...sta.de>, linux-kernel@...r.kernel.org Subject: Re: 2.6.21-rc suspend regression: sysfs deadlock Am Mittwoch, 7. März 2007 17:52 schrieb Linus Torvalds: > > On Wed, 7 Mar 2007, Dmitry Torokhov wrote: > > > > ... with the exception that it will again make data associated with > > sysfs attributes accessible past the point of returning from > > sysfs_remove_file. And that was the point so drivers would not have to > > care about handling access to extra data (such as static strings) past > > the driver unload. > > Drivers are unloaded by stopping the whole machine (exactly because module > unload is otherwise so hard to handle), so that never happens unless you > actively block. In other words, if you do something as simple as The problem also exists with unplugging devices. Drivers get no feedback to tell them when it is safe to free the data structures associated with an attribute. Regards Oliver - 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