From: Daniel Phillips <phillips@istop.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Joel Becker <Joel.Becker@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Permissions don't stick on ConfigFS attributes
Date: Sat, 20 Aug 2005 16:21:01 +1000 [thread overview]
Message-ID: <200508201621.02151.phillips@istop.com> (raw)
In-Reply-To: <9e473391050819182249e67dea@mail.gmail.com>
On Saturday 20 August 2005 11:22, Jon Smirl wrote:
> A patch for making sysfs attributes persistent has recently made it
> into Linus' tree.
>
>
http://article.gmane.org/gmane.linux.hotplug.devel/7927/match=sysfs+permissions
Interesting, it handles more than just the file mode. But does anybody really
care about the ctime/atime/mtime in sysfs? I can see how uid and gid could
be useful. My way of handling this (by copying out the potentially changed
iattrs when the dentry is destroyed) looks more compact than Maneesh's
solution, while not being any less effective, once I get it right that is.
Does sysfs really need its own setattr?
A quibble: we normally use the term persistent to mean "saved on permanent
storage". Going by that, Maneesh just fixed a bug and did not make iattrs
persistent.
Regards,
Daniel
next prev parent reply other threads:[~2005-08-20 6:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 0:50 [PATCH] Permissions don't stick on ConfigFS attributes Daniel Phillips
2005-08-20 1:22 ` Jon Smirl
2005-08-20 6:21 ` Daniel Phillips [this message]
2005-08-20 3:01 ` Greg KH
2005-08-20 3:23 ` Daniel Phillips
2005-08-20 3:33 ` Greg KH
2005-08-20 5:41 ` Daniel Phillips
2005-08-20 6:31 ` Joel Becker
2005-08-20 7:35 ` Daniel Phillips
2005-08-20 21:09 ` [PATCH] Permissions don't stick on ConfigFS attributes (revised) Daniel Phillips
2005-08-22 4:49 ` [PATCH] Permissions don't stick on ConfigFS attributes Eric W. Biederman
2005-08-22 19:44 ` Daniel Phillips
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=200508201621.02151.phillips@istop.com \
--to=phillips@istop.com \
--cc=Joel.Becker@oracle.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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