From: Mike Waychison <mike@waychison.com>
To: Ian Kent <raven@themaw.net>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
jamie@shareable.org,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Subject: Re: [RFC][PATCH 1/8] namespace: use global namespace semaphore
Date: Fri, 03 Jun 2005 10:24:08 -0700 [thread overview]
Message-ID: <42A09238.7080204@waychison.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506011224450.10849@wombat.indigo.net.au>
Ian Kent wrote:
> On Tue, 31 May 2005, Miklos Szeredi wrote:
>
>
>>>There's not really anything magic about using the follow link method. It's
>>>just a bit of a cheat as a directory can't also be a symlink and the
>>>callback comes at exactly the right time to make stuff happen.
>>
>>So is it something like this?
>>
>> - autofs is mounted over direct mountpoint 'dm'
>>
>> - when dm is looked up, autofs's follow_link method is called
>>
>> - this triggers the actual mount in the daemon, which mounts over
>> the autofs filesystem (with some trick to avoid recursion)
>
>
> Admit, I haven't paid enough attention to recursion.
> Ouch! Caught by that the other day.
>
>
>> - when the daemon is finished, the autofs's follow_link method
>> enters the new mount (how?) and returns
>
>
> A function functionally similar to follow_mount of namei.c. Which needs
> the appropriate vfsmount.
>
>
>>
>>Why do you need the mount topology for this?
>
>
> Don't. Actually need the nameidata upto date when the follow_link method
> is called.
>
However you can't rely on this for expiry checks, as the vfsmount can
change (--rbind, CLONE_NEWNS).
Mike Waychison
next prev parent reply other threads:[~2005-06-03 17:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 13:19 [RFC][PATCH 1/8] namespace: use global namespace semaphore Miklos Szeredi
2005-05-31 2:58 ` Ian Kent
2005-05-31 3:23 ` Mike Waychison
2005-05-31 7:02 ` Ian Kent
2005-05-31 7:56 ` Miklos Szeredi
2005-05-31 9:34 ` Ian Kent
2005-05-31 10:05 ` Miklos Szeredi
2005-05-31 10:13 ` Miklos Szeredi
2005-05-31 15:43 ` Mike Waychison
2005-06-01 5:04 ` Ian Kent
2005-06-01 8:35 ` Miklos Szeredi
2005-06-03 2:10 ` Ian Kent
2005-06-03 5:28 ` Miklos Szeredi
2005-06-04 4:13 ` raven
2005-06-04 6:32 ` Miklos Szeredi
2005-06-04 6:50 ` raven
2005-06-04 7:20 ` Miklos Szeredi
2005-06-04 7:27 ` raven
2005-06-03 17:22 ` Mike Waychison
2005-06-04 4:32 ` raven
2005-06-03 17:13 ` Mike Waychison
2005-06-03 18:20 ` Miklos Szeredi
2005-06-01 4:36 ` Ian Kent
2005-06-03 17:24 ` Mike Waychison [this message]
2005-06-04 4:38 ` raven
2005-05-31 15:55 ` Mike Waychison
2005-05-31 16:08 ` Miklos Szeredi
2005-06-01 4:18 ` Ian Kent
2005-06-01 8:28 ` Miklos Szeredi
2005-06-03 2:23 ` Ian Kent
2005-06-03 5:18 ` Miklos Szeredi
2005-06-04 4:53 ` raven
2005-06-04 6:57 ` Miklos Szeredi
2005-06-04 7:13 ` raven
2005-06-03 17:26 ` Mike Waychison
2005-06-01 3:57 ` Ian Kent
2005-06-03 17:07 ` Mike Waychison
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=42A09238.7080204@waychison.com \
--to=mike@waychison.com \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.net \
--cc=viro@parcelfarce.linux.theplanet.co.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).