public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@warthog.cambridge.redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: David Howells <dhowells@cambridge.redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VFS autmounter support
Date: Thu, 19 Jun 2003 08:20:06 +0100	[thread overview]
Message-ID: <2849.1056007206@warthog.warthog> (raw)
In-Reply-To: Message from "H. Peter Anvin" <hpa@zytor.com>  of "Wed, 18 Jun 2003 10:16:33 PDT." <3EF09E71.8020406@zytor.com>


> > That _is_ actually true. Doing "ls -l" in that directory would otherwise
> > cause a mount storm.
> > 
> 
> It's not.  ls -l and all the GUI tools do lstat(), not stat().

Sorry... you're correct. That should have been "ls -F" or "ls --color", both
of which are, I believe, commonly used - _they_ definitely use stat() as well
as lstat().

> > follow_link resolving to itself? Surely that'll cause ELOOP very quickly?
> > And where does this "dummy directory inode" live?
> 
> Nope.  You can follow_link() nonrecursively.  You need a dummy directory 
> inode to mount upon anyway.

You're right about follow_link() not recursing... it would have to recurse
itself, and so can avoid that. However, if it only ever follows to itself, how
does that help? That never actually gets you anywhere... It needs to trigger a
mount at some point.

Or do you mean it should follow to an arbitrary (disconnected, otherwise it
changes the topology from what the AFS admin required) dentry with a dummy
directory inode attached to it?

David

  reply	other threads:[~2003-06-19  7:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-17 14:55 [PATCH] VFS autmounter support David Howells
2003-06-17 16:08 ` H. Peter Anvin
2003-06-17 18:07   ` David Howells
2003-06-17 18:19     ` H. Peter Anvin
2003-06-18  8:37       ` David Howells
2003-06-18  8:48         ` viro
2003-06-18 17:16         ` H. Peter Anvin
2003-06-19  7:20           ` David Howells [this message]
2003-06-19  7:30             ` H. Peter Anvin
2003-06-24 15:23               ` David Howells
2003-06-18  4:55 ` Linus Torvalds
2003-06-18  5:10   ` viro
2003-06-18  7:55     ` David Howells
2003-06-18  8:36       ` viro
2003-06-18 11:01         ` David Howells

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=2849.1056007206@warthog.warthog \
    --to=dhowells@warthog.cambridge.redhat.com \
    --cc=dhowells@cambridge.redhat.com \
    --cc=hpa@zytor.com \
    --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