From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: John Ogness <dazukocode@ogness.net>,
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: Thu, 12 Feb 2009 16:47:26 +0000 [thread overview]
Message-ID: <20090212164726.GH28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LSU.2.00.0902121640580.5658@fbirervta.pbzchgretzou.qr>
On Thu, Feb 12, 2009 at 04:59:41PM +0100, Jan Engelhardt wrote:
>
> On Thursday 2009-02-12 16:31, Al Viro wrote:
> >On Thu, Feb 12, 2009 at 04:27:14PM +0100, Jan Engelhardt wrote:
> >
> >> This ought to be done better in light of the problem that one
> >> could issue `mount -t dazukofs /mnt /opt`
> >> In kernel code, I'm thinking something like
> >>
> >> static int foofs_dothis(...)
> >> {
> >> buf = call d_path on sb->s_root
> >
> >Call what on what? There is no such thing as the mountpoint of superblock.
> >
> In fs/namespace.c:do_new_mount there is 'path'. If 'path' was passed
> down to the filesystem, path->dentry, I would assume, could be used
> by the filesystem as a pointer to the original directory which
> dazuko is going to shadow.
It will not be passed dow to the filesystem, simply because said filesystem
can be silently moved elesewhere and whatever it used to be mounted on -
unmounted.
What's more, whatever it shadows might itself be mounted in any number of
places, so...
next prev parent reply other threads:[~2009-02-12 16:47 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 [this message]
2009-02-13 19:31 ` John Ogness
2009-02-13 19:48 ` Al Viro
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=20090212164726.GH28946@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox