From: ebiederm@xmission.com (Eric W. Biederman)
To: Tomas Bortoli <tomasbortoli@hotmail.it>
Cc: Richard Weinberger <richard@nod.at>,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: ext3 and like, mount point in module
Date: Wed, 05 Aug 2015 12:17:06 -0500 [thread overview]
Message-ID: <87a8u5venh.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <DUB109-W219C6838C8E2EF1B55509B6890@phx.gbl> (Tomas Bortoli's message of "Sat, 1 Aug 2015 16:34:17 +0200")
Tomas Bortoli <tomasbortoli@hotmail.it> writes:
>> What about chroot/namespaces/etc? :)
>
> I think chroot would work even so. Why would a program call chroot("..") on the root dir of the root fs?
> It's unnecessary and tricky. A local program has all the information to know relative paths and move consequently.
> Anyway it is possible.
>
>
>> I'm not sure if it is worth the hassle, I bet some applications depend on that behavior.
>> But you can give it a try, I'd insert a negative dentry for ".." if ".." is child of the current
>> root.
>
> If with negative dentry you mean not putting ".." I've understood.
> But, ".." is needed for file system mounted not on the root point, otherwise they would be disconnected from the "parent" fs.
> So, the "mount_point" variable is needed and it is not present in the file system module itself, as you said.
> Where can I find the vfs module?
> And, If I've understood what Al Viro said, it's correct to work on vfs rather than on the specific file system module.
fs/namei.c follow_dotdot and follow_dotdot_rcu
You might also take a gander at the patches I have recently posted that
address a similiar but different issue with .. and bind mounts. That
should at least show you where the code is.
Eric
prev parent reply other threads:[~2015-08-05 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 12:27 ext3 and like, mount point in module Tomas Bortoli
2015-08-01 12:46 ` Richard Weinberger
2015-08-01 13:10 ` Tomas Bortoli
2015-08-01 13:27 ` Richard Weinberger
2015-08-01 13:43 ` Al Viro
2015-08-01 14:34 ` Tomas Bortoli
2015-08-05 17:17 ` Eric W. Biederman [this message]
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=87a8u5venh.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=richard@nod.at \
--cc=tomasbortoli@hotmail.it \
/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