From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hughd@google.com
Subject: Re: [PATCH] TMPFS: Expand "help" to explain value of TMPFS_POSIX_ACL
Date: Sat, 18 Jun 2011 11:03:35 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1106181102550.3659@localhost6.localdomain6> (raw)
In-Reply-To: <20110618075301.b4d3816c.rdunlap@xenotime.net>
On Sat, 18 Jun 2011, Randy Dunlap wrote:
> On Sat, 18 Jun 2011 07:45:35 -0400 (EDT) Robert P. J. Day wrote:
>
> >
> > Expand the fs/Kconfig "help" info to clarify why it's a bad idea to
> > deselect the TMPFS_POSIX_ACL config variable.
> >
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> >
> > ---
> >
> > diff --git a/fs/Kconfig b/fs/Kconfig
> > index 19891aa..4217543 100644
> > --- a/fs/Kconfig
> > +++ b/fs/Kconfig
> > @@ -127,14 +127,20 @@ config TMPFS_POSIX_ACL
> > select TMPFS_XATTR
> > select GENERIC_ACL
> > help
> > - POSIX Access Control Lists (ACLs) support permissions for users and
> > - groups beyond the owner/group/world scheme.
> > + POSIX Access Control Lists (ACLs) support additional access rights
> > + for users and groups beyond the standard owner/group/world scheme,
> > + and this option selects support for ACLs specifically for tmpfs
> > + filesystems.
> > +
> > + If you've selected TMPFS, you almost certainly want this option
> > + as well since a number of user space features (ie., ALSA sound)
>
> e.g.,
> ?
>
> Otherwise, looks good to me.
> Thanks.
oops, i can submit a V2 patch that changes that. or you can hack
what i submitted. either way works for me.
rday
next prev parent reply other threads:[~2011-06-18 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 11:45 Robert P. J. Day
2011-06-18 14:53 ` Randy Dunlap
2011-06-18 15:03 ` Robert P. J. Day [this message]
2011-06-18 15:05 ` Randy Dunlap
2011-06-18 17:28 ` Stefan Richter
2011-06-18 17:32 ` Robert P. J. Day
2011-06-18 17:37 ` Randy Dunlap
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=alpine.DEB.2.02.1106181102550.3659@localhost6.localdomain6 \
--to=rpjday@crashcourse.ca \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®