From: Alan Stern <stern@rowland.harvard.edu>
To: Oliver Neukum <oneukum@suse.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Maneesh Soni <maneesh@in.ibm.com>, <gregkh@suse.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: refcounting drivers' data structures used in sysfs buffers
Date: Mon, 12 Mar 2007 16:03:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0703121557360.4003-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <200703122049.03113.oneukum@suse.de>
On Mon, 12 Mar 2007, Oliver Neukum wrote:
> > > I don't like reverting my own code. But I predict he'll tell you that a
> > > driver's bond with a device should be represented in a data structure
> > > that is to be refcounted.
> >
> > :-)
>
> Coming to think about it, he might be right there.
There still would be a synchronization problem. Refcounts don't solve
races; they only solve lifetime problems. And you would still have to
change the sysfs API, plus all the other stuff...
Do you think Linus would listen if all three of us (plus maybe Greg) tried
to convince him?
Alan Stern
next prev parent reply other threads:[~2007-03-12 20:03 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 13:05 refcounting drivers' data structures used in sysfs buffers Oliver Neukum
2007-03-08 16:02 ` Alan Stern
2007-03-09 0:45 ` Oliver Neukum
2007-03-09 16:32 ` Alan Stern
2007-03-09 16:44 ` Oliver Neukum
2007-03-09 17:02 ` Dmitry Torokhov
2007-03-09 17:18 ` Oliver Neukum
2007-03-09 17:34 ` Dmitry Torokhov
2007-03-09 19:32 ` Alan Stern
2007-03-09 20:05 ` Oliver Neukum
2007-03-09 20:27 ` Alan Stern
2007-03-09 20:39 ` Oliver Neukum
2007-03-09 20:08 ` Alan Stern
2007-03-09 20:48 ` Oliver Neukum
2007-03-10 19:19 ` Alan Stern
2007-03-12 8:54 ` Oliver Neukum
2007-03-12 14:57 ` Alan Stern
2007-03-12 15:23 ` Oliver Neukum
2007-03-12 15:42 ` Dmitry Torokhov
2007-03-12 15:59 ` Oliver Neukum
2007-03-12 16:21 ` Alan Stern
2007-03-12 18:25 ` Oliver Neukum
2007-03-12 19:31 ` Alan Stern
2007-03-12 19:49 ` Oliver Neukum
2007-03-12 20:03 ` Alan Stern [this message]
2007-03-12 20:15 ` Oliver Neukum
2007-03-12 20:31 ` Dmitry Torokhov
2007-03-12 20:45 ` Alan Stern
2007-03-12 21:31 ` Richard Purdie
2007-03-13 15:00 ` 2.6.21-rc suspend regression: sysfs deadlock Alan Stern
2007-03-13 18:42 ` Cornelia Huck
2007-03-13 21:20 ` Linus Torvalds
2007-03-14 16:12 ` Alan Stern
2007-03-14 18:43 ` Cornelia Huck
2007-03-14 19:23 ` Alan Stern
2007-03-15 10:27 ` Cornelia Huck
2007-03-15 12:31 ` Hugh Dickins
2007-03-15 13:02 ` Oliver Neukum
2007-03-15 13:22 ` Dmitry Torokhov
2007-03-15 13:59 ` Hugh Dickins
2007-03-15 14:27 ` Alan Stern
2007-03-15 15:32 ` Cornelia Huck
2007-03-15 16:29 ` Hugh Dickins
2007-03-15 16:51 ` Linus Torvalds
2007-03-15 19:50 ` [PATCH] sysfs and driver core: add callback helper, used by SCSI and S390 Alan Stern
2007-03-15 19:51 ` [PATCH] sysfs: reinstate exclusion between method calls and attribute unregistration Alan Stern
2007-03-13 19:00 ` 2.6.21-rc suspend regression: sysfs deadlock Hugh Dickins
2007-03-13 20:09 ` Alan Stern
2007-03-13 20:55 ` Hugh Dickins
2007-03-13 21:08 ` Dmitry Torokhov
2007-03-13 21:20 ` Alan Stern
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=Pine.LNX.4.44L0.0703121557360.4003-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=oneukum@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).