From: Greg KH <gregkh@suse.de>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: linux-kernel@vger.kernel.org, Kees Cook <kees.cook@canonical.com>,
Eugene Teo <eugeneteo@gmail.com>
Subject: Re: [RFC] add mount options to sysfs
Date: Fri, 20 May 2011 06:54:24 -0700 [thread overview]
Message-ID: <20110520135424.GA10878@suse.de> (raw)
In-Reply-To: <20110520133615.GB8112@albatros>
On Fri, May 20, 2011 at 05:36:15PM +0400, Vasiliy Kulikov wrote:
> On Fri, May 20, 2011 at 17:34 +0400, Vasiliy Kulikov wrote:
> > On Fri, May 20, 2011 at 06:30 -0700, Greg KH wrote:
> > > > Correct. So, if I understood you, you are OK with adding mount options
> > > > for debugfs, but not sysfs, right? What is the difference between them
> > > > in sense of permissions?
> > >
> > > debugfs is "there are no rules", so changing the permissions on it
> > > shouldn't break anything as no userspace tools "should" rely on it. Now
> > > that really isn't true (see the perf stuff), but overall it is, so I
> > > don't worry about changing things there as much as sysfs, which has
> > > hundreds of tools relying on it.
> >
> > What would break if the default behaviour is not changed?
>
> Err... sorry, s/would break/would it break/
That's the question for you, we would be changing the kernel/user api
here, and odds are, something will break.
thansk,
greg k-h
next prev parent reply other threads:[~2011-05-20 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 16:31 [RFC] add mount options to sysfs Vasiliy Kulikov
2011-05-18 16:39 ` Greg KH
2011-05-18 17:05 ` Vasiliy Kulikov
2011-05-18 19:17 ` Greg KH
2011-05-19 6:26 ` Vasiliy Kulikov
2011-05-19 17:12 ` Greg KH
2011-05-20 9:59 ` Vasiliy Kulikov
2011-05-20 13:30 ` Greg KH
2011-05-20 13:34 ` Vasiliy Kulikov
2011-05-20 13:36 ` Vasiliy Kulikov
2011-05-20 13:54 ` Greg KH [this message]
2011-05-20 15:17 ` Kees Cook
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=20110520135424.GA10878@suse.de \
--to=gregkh@suse.de \
--cc=eugeneteo@gmail.com \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=segoon@openwall.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).