From: Al Viro <viro@ZenIV.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Karel Zak <kzak@redhat.com>,
dhowells@redhat.com, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: Re: d_path() and overlay fs
Date: Fri, 20 Mar 2015 16:25:58 +0000 [thread overview]
Message-ID: <20150320162558.GA29656@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20150320160123.GE20913@tucsk>
On Fri, Mar 20, 2015 at 05:01:23PM +0100, Miklos Szeredi wrote:
> But it does take care of the majority of f_path users that actually want the
> covering path.
Bloody bad idea, IMO. I have no objections against adding _helpers_ from
that patch (seq_file_path(), etc.), but I really don't like adding that
second struct path there. And it still doesn't fix the issue with
LSM, etc., so we'll _still_ need to fix it sane way.
next prev parent reply other threads:[~2015-03-20 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 13:29 d_path() and overlay fs Karel Zak
2015-03-20 13:31 ` Al Viro
2015-03-20 13:41 ` Josh Boyer
2015-03-20 16:01 ` Miklos Szeredi
2015-03-20 16:25 ` Al Viro [this message]
2015-03-20 16:53 ` Miklos Szeredi
2015-03-20 18:16 ` Miklos Szeredi
2016-01-06 5:26 ` sangeetha Busangari
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=20150320162558.GA29656@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dhowells@redhat.com \
--cc=jwboyer@fedoraproject.org \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.