From: Oliver Neukum <oliver@neukum.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Maneesh Soni <maneesh@in.ibm.com>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Fwd: Re: 2.6.21-rc suspend regression: sysfs deadlock
Date: Fri, 9 Mar 2007 01:41:10 +0100 [thread overview]
Message-ID: <200703090141.11044.oliver@neukum.org> (raw)
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@linux-foundation.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, Hugh Dickins <hugh@veritas.com>, Oliver Neukum <oliver@neukum.name>, Maneesh Soni <maneesh@in.ibm.com>, Greg Kroah-Hartman <gregkh@suse.de>, Adrian Bunk <bunk@stusta.de>, linux-kernel@vger.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
-------------------------------------------------------
reply other threads:[~2007-03-09 0:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200703090141.11044.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®