public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: jmorris@redhat.com, sds@epoch.ncsc.mil, linux-kernel@vger.kernel.org
Subject: Re: [SELINUX] Handle fuse binary mount data.
Date: Sun, 29 Feb 2004 15:02:13 -0800	[thread overview]
Message-ID: <20040229150213.3ebd7ef9.akpm@osdl.org> (raw)
In-Reply-To: <20040229215542.A31786@infradead.org>

Christoph Hellwig <hch@infradead.org> wrote:
>
> On Sun, Feb 29, 2004 at 04:38:51PM -0500, James Morris wrote:
> >  	/* Ignore these fileystems with binary mount option data. */
> > -	if (!strcmp(name, "coda") ||
> > -	    !strcmp(name, "afs") || !strcmp(name, "smbfs"))
> > +	if (!strcmp(name, "coda") || !strcmp(name, "afs") ||
> > +	    !strcmp(name, "smbfs") || !strcmp(name, "fuse"))
> >  		goto out;
> 
> Umm, binary mount data is bad enough, but hardcoding filesystem-depend code
> in selinux is just bogus..

Yes, it's rather awkward.

Could we do something such as passing a new mount flag in from userspace? 
Add a new flag alongside MS_SYNCHRONOUS, MS_REMOUNT and friends?

  reply	other threads:[~2004-02-29 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 21:38 [SELINUX] Handle fuse binary mount data James Morris
2004-02-29 21:55 ` Christoph Hellwig
2004-02-29 23:02   ` Andrew Morton [this message]
2004-02-29 23:41     ` H. Peter Anvin
2004-03-01  1:24     ` James Morris
2004-03-01  1:59       ` H. Peter Anvin
2004-03-01  9:48       ` Urban Widmark
2004-03-01 13:15         ` James Morris
2004-03-01 19:52           ` Urban Widmark

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=20040229150213.3ebd7ef9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    /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