public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: VFS + path walktrough
Date: Mon, 5 May 2008 21:02:43 +0200	[thread overview]
Message-ID: <20080505190243.GI32019@nibiru.local> (raw)
In-Reply-To: <20080505183420.GQ5882@ZenIV.linux.org.uk>

* Al Viro <viro@ZenIV.linux.org.uk> wrote:

> 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?

In the same way as, eg. http servers, do. Of course this fails 
if the symlink isn't resolvable within server's fs.

Several years ago, I've seen exactly this behaviour on Samba.
Whether this is what you might expect, is another story ;-P

> > Naive question: is it really *necessary* to have all the 
> > intermediate dirs in dcache ?
> 
> The answer's "yes".

What exactly are they needed for ? 
Which information is needed ?
Can we perhaps fake them (at least we know - on success - the
intermediate components are dirs) ?


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------

  reply	other threads:[~2008-05-05 19:04 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
2008-05-05 19:02                     ` Enrico Weigelt [this message]
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=20080505190243.GI32019@nibiru.local \
    --to=weigelt@metux.de \
    --cc=linux-kernel@vger.kernel.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