From: Greg KH <greg@kroah.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: viro@parcelfarce.linux.theplanet.co.uk,
Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc1
Date: Sat, 7 Feb 2004 11:20:28 -0800 [thread overview]
Message-ID: <20040207192027.GD2581@kroah.com> (raw)
In-Reply-To: <20040207172152.GA6412@arizona.localdomain>
On Sat, Feb 07, 2004 at 12:21:52PM -0500, Kevin O'Connor wrote:
>
> So, my question - is it really a good idea to rework much of the kernel
> object lifetime rules just to support sysfs?
At this point in time, in the stable kernel series, I say no.
That is why I created the class_simple interface, which allows
developers to be able to export data through sysfs (like the dev_t
data), without having to change their lifetime rules at all.
Now when 2.7 starts up again, that's the proper time to be changing this
kind of stuff to work "properly". Until then, lets just live with the
lifetime rules that we have (if they work, and almost all of them seem
to).
And remember, I'm the person who really _wants_ to see all of this stuff
fixed up properly...
> And a related question - couldn't sysfs be taught to atomically drop its
> references to external kernel objects and thus obviate the need for all
> these lifetime rule changes?
See the class_simple code for an example of how this can be done. It's
not a sysfs issue. It's an issue of how you _use_ sysfs :)
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-07 19:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 2:28 Linux 2.6.3-rc1 Linus Torvalds
2004-02-07 2:56 ` viro
2004-02-07 17:21 ` Kevin O'Connor
2004-02-07 19:20 ` Greg KH [this message]
2004-02-07 3:11 ` Måns Rullgård
2004-02-07 5:26 ` Greg KH
2004-02-07 10:24 ` Andre Tomt
2004-02-07 16:22 ` Bartlomiej Zolnierkiewicz
2004-02-08 6:02 ` Andre Tomt
2004-02-08 6:29 ` Andre Tomt
2004-02-08 21:34 ` Bartlomiej Zolnierkiewicz
2004-02-08 21:55 ` Andre Tomt
2004-02-08 22:51 ` Bartlomiej Zolnierkiewicz
2004-02-09 0:08 ` Andre Tomt
2004-02-09 1:34 ` Bartlomiej Zolnierkiewicz
2004-02-09 2:40 ` Andre Tomt
2004-02-09 12:41 ` Arkadiusz Miskiewicz
2004-02-09 14:41 ` Bartlomiej Zolnierkiewicz
2004-02-09 13:01 ` Bartlomiej Zolnierkiewicz
2004-02-09 1:53 ` Disassembling with gdb (Re: Linux 2.6.3-rc1) Matthew Reppert
2004-02-08 15:18 ` Linux 2.6.3-rc1 Geert Uytterhoeven
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=20040207192027.GD2581@kroah.com \
--to=greg@kroah.com \
--cc=kevin@koconnor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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