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

David Howells wrote:
>>
>>That's actually not true.  It's lstat() that mustn't cause the automount
>>point to mount -- stat() only comes into play if lstat() resolves to a
>>symlink.  However, lstat() never invokes follow_link, so creating a
>>dentry with a follow_link method resolving to itself, and an associated
>>dummy directory inode, does what's required.
> 
> 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().

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

	-hpa


  parent reply	other threads:[~2003-06-18 17:02 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 [this message]
2003-06-19  7:20           ` David Howells
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=3EF09E71.8020406@zytor.com \
    --to=hpa@zytor.com \
    --cc=dhowells@cambridge.redhat.com \
    --cc=dhowells@warthog.cambridge.redhat.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