From: Jon Smirl <jonsmirl@gmail.com>
To: Daniel Phillips <phillips@istop.com>
Cc: Joel Becker <Joel.Becker@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Permissions don't stick on ConfigFS attributes
Date: Fri, 19 Aug 2005 21:22:30 -0400 [thread overview]
Message-ID: <9e473391050819182249e67dea@mail.gmail.com> (raw)
In-Reply-To: <200508201050.51982.phillips@istop.com>
On 8/19/05, Daniel Phillips <phillips@istop.com> wrote:
> Hi Joel,
>
> Permissions set on ConfigFS attributes (aka files) do not stick. The reason
> is that configfs attribute inodes are not pinned and simply disappear after
> each file operation. This is good because it saves memory, but it is not
> good to throw the permissions away - you then don't have any way to expose
> configuration tweaks to normal users. The patch below fixes this by copying
> each file's mode back into the non-transient backing structure on dentry
> delete.
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
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-08-20 1:22 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 [this message]
2005-08-20 6:21 ` Daniel Phillips
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=9e473391050819182249e67dea@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Joel.Becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@istop.com \
/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.