[<prev] [next>] [day] [month] [year] [list]
Message-Id: <200703090141.11044.oliver@neukum.org>
Date: Fri, 9 Mar 2007 01:41:10 +0100
From: Oliver Neukum <oliver@...kum.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Maneesh Soni <maneesh@...ibm.com>, gregkh@...e.de,
linux-kernel@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>
Subject: Fwd: Re: 2.6.21-rc suspend regression: sysfs deadlock
To let you hear the verdict.
Regards
Oliver
---------- Weitergeleitete Nachricht ----------
Subject: Re: 2.6.21-rc suspend regression: sysfs deadlock
Date: Mittwoch, 7. März 2007 19:02
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Oliver Neukum <oliver@...kum.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
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.
Linus
-------------------------------------------------------
-
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