From: Al Viro <viro@ZenIV.linux.org.uk>
To: Enrico Weigelt <weigelt@metux.de>
Cc: linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: VFS + path walktrough
Date: Mon, 5 May 2008 19:34:20 +0100 [thread overview]
Message-ID: <20080505183420.GQ5882@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20080505182308.GG32019@nibiru.local>
On Mon, May 05, 2008 at 08:23:09PM +0200, Enrico Weigelt wrote:
> Assuming the server doesn't resolve symlinks itself,
Um... What the hell are you talking about? How _can_ server resolve
symlinks, when result of symlink resolution depends on where the damn
thing is mounted on client and even how deeply the process trying to
do lookup happens to be chrooted?
It wouldn't work even for relative symlinks - remember that we might
bloody well have something bound on the middle of the path in question.
Without any knowledge by fs.
> Naive question: is it really *necessary* to have all the
> intermediate dirs in dcache ?
The answer's "yes".
next prev parent reply other threads:[~2008-05-05 18:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 12:40 VFS + path walktrough Enrico Weigelt
2008-05-05 13:06 ` Enrico Weigelt
2008-05-05 13:13 ` Al Viro
2008-05-05 13:43 ` Enrico Weigelt
2008-05-05 15:35 ` Al Viro
2008-05-05 16:43 ` Miklos Szeredi
2008-05-05 17:03 ` Miklos Szeredi
2008-05-05 17:14 ` Al Viro
2008-05-05 17:33 ` Miklos Szeredi
2008-05-05 17:40 ` Al Viro
2008-05-05 18:03 ` Miklos Szeredi
2008-05-05 18:31 ` Miklos Szeredi
2008-05-05 20:16 ` Trond Myklebust
2008-05-05 20:35 ` Miklos Szeredi
2008-05-05 18:50 ` Enrico Weigelt
2008-05-05 18:23 ` Enrico Weigelt
2008-05-05 18:34 ` Al Viro [this message]
2008-05-05 19:02 ` Enrico Weigelt
2008-05-05 19:09 ` 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=20080505183420.GQ5882@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=weigelt@metux.de \
/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