From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: Inconsistency in sysfs behavior?
Date: Wed, 7 Jan 2004 13:56:24 -0800 [thread overview]
Message-ID: <20040107215624.GC1083@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0401071644220.1589-100000@ida.rowland.org>
On Wed, Jan 07, 2004 at 04:50:24PM -0500, Alan Stern wrote:
> On Wed, 7 Jan 2004, Greg KH wrote:
>
> > Because it is very difficult to determine when a user goes into a
> > directory because we are using the ramfs/libfs code. It also does not
> > cause any errors if the kobject is removed, as the vfs cleans up
> > properly.
> >
> > Only when a file is opened does a kobject need to be pinned, due to
> > possible errors that could happen.
>
> I had in mind approaching this the opposite way. Instead of trying to
> make open directories also pin a kobject, why not make open attribute
> files not pin them?
>
> It shouldn't be hard to avoid any errors; in fact I had a patch from some
> time ago that would do the trick (although in a hacked-up kind of way).
> The main idea is to return -ENXIO instead of calling the show()/store()
> routines once the attribute has been removed.
And you can do this without adding another lock, race free?
greg k-h
next prev parent reply other threads:[~2004-01-07 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 15:48 Inconsistency in sysfs behavior? Alan Stern
2004-01-07 17:27 ` Greg KH
2004-01-07 21:50 ` Alan Stern
2004-01-07 21:56 ` Greg KH [this message]
2004-01-07 22:24 ` Alan Stern
2004-01-07 22:34 ` Greg KH
2004-01-08 10:32 ` Maneesh Soni
2004-01-08 20:19 ` Greg KH
2004-01-09 4:56 ` Maneesh Soni
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=20040107215624.GC1083@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.