From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC] readlink()-related oddities
Date: Fri, 20 Nov 2015 03:24:53 +0000 [thread overview]
Message-ID: <20151120032451.GK22011@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFy=__75U59zj0G7fqU5AjZO_FEEE=bqt7bk+4S41NLHgg@mail.gmail.com>
On Thu, Nov 19, 2015 at 07:16:32PM -0800, Linus Torvalds wrote:
> .. it's not necessarily just readlink() either. I still think it might
> be a perfectly fine idea to allow non-directories to act as
> directories in some case (by exposing "readdir" and "lookup").
As soon as we expose ->lookup(), we are in for serious PITA with locking.
Please, don't. The situation is convoluted enough as it is; playing with
parallel lookups is going to be interesting in itself and I'd rather not
mix it with attempts to accomodate for hybrid objects (e.g. something
with children and more than one parent, etc.), especially since I'm not
sure the latter can be done without major pain.
next prev parent reply other threads:[~2015-11-20 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 23:26 [RFC] readlink()-related oddities Al Viro
2015-11-20 2:13 ` Linus Torvalds
2015-11-20 2:57 ` Al Viro
2015-11-20 3:09 ` Linus Torvalds
2015-11-20 3:16 ` Linus Torvalds
2015-11-20 3:24 ` Al Viro [this message]
2015-11-20 10:00 ` David Howells
2015-11-20 9:59 ` David Howells
2015-11-20 16:08 ` Al Viro
2015-11-20 16:26 ` David Howells
2015-11-20 22:33 ` Al Viro
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=20151120032451.GK22011@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).