| 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: <200703071916.57907.oliver@neukum.org> Date: Wed, 7 Mar 2007 19:16:57 +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>, 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 19:02 schrieb Linus Torvalds: > > On Wed, 7 Mar 2007, Oliver Neukum wrote: > > > > 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. > > So you just pointed to *another* data structure that apparently violates > the "you MUST use refcounting" rule. > > What is it with you people? It's really simple. Data structures must be > refcounted if you can reach them two different ways. > > If you don't use refcounting, then you'd better make sure that the data > can be reached only one way (for example, by *not* exposing it for sysfs). > > It really *is* that simple. Read the CodingStyle rules. Very well, there seems to be no clean way to avoid that work. 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