From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
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: Thu, 19 Nov 2015 19:09:20 -0800 [thread overview]
Message-ID: <CA+55aFyWTDZxATj=WbX_X-Eb=mCO9s=ULZdPmyQRXNGQOgbBZw@mail.gmail.com> (raw)
In-Reply-To: <20151120025749.GJ22011@ZenIV.linux.org.uk>
On Thu, Nov 19, 2015 at 6:57 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> How would those tools know that this particular pathname _is_ a magical
> symlink?
Like maybe just the AFS management tools? By design you'd only run
them on the mountpoint in question.
Not everything has to be "generic". Sometimes its' good enough to just
have the ability to get the work done.
Now, if it turns out that others also want to do this, maybe somebody
decides "let's add flag -V to 'ls', which forces a 'readlink()' on all
the targets, whether links or not, and shows the information".
I could imagine other special files having "a single line of
information about the file" that they'd expose with readlink(). Who
knows?
So there is *potential* for just making it generic, but that doesn't
mean that it necessarily has to act that way.
Linus
next prev parent reply other threads:[~2015-11-20 3:09 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 [this message]
2015-11-20 3:16 ` Linus Torvalds
2015-11-20 3:24 ` Al Viro
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='CA+55aFyWTDZxATj=WbX_X-Eb=mCO9s=ULZdPmyQRXNGQOgbBZw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--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=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;
as well as URLs for NNTP newsgroup(s).