From: Evgeniy Polyakov <zbr@ioremap.net>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Joe Perches <joe@perches.com>,
greg@kroah.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [take 3] pohmelfs: call for inclusion
Date: Thu, 22 Mar 2012 02:40:02 +0400 [thread overview]
Message-ID: <20120321224001.GB23336@ioremap.net> (raw)
In-Reply-To: <20120321222812.GS6589@ZenIV.linux.org.uk>
On Wed, Mar 21, 2012 at 10:28:12PM +0000, Al Viro (viro@ZenIV.linux.org.uk) wrote:
> Sigh... I wish it hadn't been an English-speaking maillist; mat is hard to
> translate properly...
Argh, undecency is pretty useful /most of the time/frequently/
> OK, let me try for a printable version: suppose we replace that d_path()
> call with dentry_path() and leave everything else as is; what exactly
> will be broken and how will it break?
I didn't understand you at first. Replacing it with dentry_path() will
not break anything. It was not supposed fs should care about chroot for
this case - every application (including chrooted) writes into own
namespace, so if it changes root, it is on its own...
> > When object was written via remounted path, then it is a problem for
> > those who made a setup - this ugly hack only 'works' in specially
> > crafted environment, which provides its pros and requires fair price of
> > cons.
>
> _What_ remounted path? I'm not talking about bindings at all...
I believe you will?
Actually if this useful hack is so much a PITA I will drop it. Or fix
with dentry_path() instead. It doesn't really deserve _that_ much.
--
Evgeniy Polyakov
prev parent reply other threads:[~2012-03-21 22:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 12:18 [take 3] pohmelfs: call for inclusion Evgeniy Polyakov
2012-03-16 13:29 ` Joe Perches
2012-03-16 13:39 ` Evgeniy Polyakov
2012-03-16 13:43 ` Evgeniy Polyakov
2012-03-16 14:12 ` Joe Perches
2012-03-21 20:27 ` Evgeniy Polyakov
2012-03-21 21:02 ` Linus Torvalds
2012-03-21 21:18 ` Al Viro
2012-03-21 21:37 ` Evgeniy Polyakov
2012-03-21 21:54 ` Al Viro
2012-03-21 22:04 ` Evgeniy Polyakov
2012-03-21 22:28 ` Al Viro
2012-03-21 22:40 ` Evgeniy Polyakov [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=20120321224001.GB23336@ioremap.net \
--to=zbr@ioremap.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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