All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: John Ogness <dazukocode@ogness.net>
Cc: Jan Engelhardt <jengelh@medozas.de>,
	linux-kernel@vger.kernel.org, malware-list@lists.printk.net,
	eparis@redhat.com, hch@infradead.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCHv2 1/5] VFS: DazukoFS, stackable-fs, file access control
Date: Fri, 13 Feb 2009 19:48:12 +0000	[thread overview]
Message-ID: <20090213194812.GM28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <86y6wagmmg.fsf@johno.fn.ogness.net>

On Fri, Feb 13, 2009 at 08:31:03PM +0100, John Ogness wrote:

> If we want to forbid users from being able to do this, I think it
> would be simpler just to fail the mount if it is _not_ specified for
> direct stacking. This forces users to use a syntax that makes it very
> clear what they are doing.
> 
> Since mounting to a different directory could cause problems, I think
> it will be good to forbid it. I will make this change for the next
> patch series.

And just how are you going to do that?  Note that underlying directory
may be visible in many places to start with...

  reply	other threads:[~2009-02-13 19:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 19:14 [PATCHv2 0/5] VFS: DazukoFS, stackable-fs, file access control John Ogness
2009-02-03 19:15 ` [PATCHv2 1/5] " John Ogness
2009-02-03 19:17   ` [PATCHv2 2/5] " John Ogness
2009-02-03 19:18     ` [PATCHv2 3/5] " John Ogness
2009-02-03 19:19       ` [PATCHv2 4/5] " John Ogness
2009-02-03 19:20         ` [PATCHv2 5/5] " John Ogness
2009-02-12 20:24           ` Eric W. Biederman
2009-02-12 20:20       ` [PATCHv2 3/5] " Eric W. Biederman
2009-02-17  8:55         ` John Ogness
2009-02-18  0:41           ` Eric W. Biederman
2009-02-21 18:11       ` [malware-list] " Frantisek Hrbata
2009-02-12 16:00     ` [PATCHv2 2/5] " Jan Engelhardt
2009-02-13 19:33       ` John Ogness
2009-02-12 20:14     ` Eric W. Biederman
2009-02-13 19:39       ` John Ogness
2009-02-12 15:27   ` [PATCHv2 1/5] " Jan Engelhardt
2009-02-12 15:31     ` Al Viro
2009-02-12 15:59       ` Jan Engelhardt
2009-02-12 16:47         ` Al Viro
2009-02-13 19:31     ` John Ogness
2009-02-13 19:48       ` Al Viro [this message]
2009-02-13 20:00       ` Jan Engelhardt
2009-02-13 20:25         ` Al Viro
2009-02-14  8:43           ` John Ogness

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=20090213194812.GM28946@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dazukocode@ogness.net \
    --cc=eparis@redhat.com \
    --cc=hch@infradead.org \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malware-list@lists.printk.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 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.