From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: jlayton@redhat.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
ebiederm@xmission.com, adobriyan@gmail.com,
viro@ZenIV.linux.org.uk, jamie@shareable.org
Subject: Re: [PATCH 0/2] vfs: ensure that dentries are revalidated on open (try #2)
Date: Wed, 11 Nov 2009 21:17:19 +0900 [thread overview]
Message-ID: <1257941839.2949.9.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <E1N88eK-0006Im-1F@pomaz-ex.szeredi.hu>
On Wed, 2009-11-11 at 09:33 +0100, Miklos Szeredi wrote:
> On Wed, 11 Nov 2009, Trond Myklebust wrote:
> > Aren't both proc symlinks and bind mounts pretty much guaranteed to
> > point to a valid dentry?
>
> It could for example happen that client bind mounts a regular file,
> then the file is unlinked on the server. Then the bind mounted dentry
> is no longer valid.
The mountpoint dentry is still supposed to remain valid and accessible
on the client even if the object it points to on the server is invalid.
Otherwise you will not be able to unmount.
Cheers
Trond
next prev parent reply other threads:[~2009-11-11 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 16:27 Jeff Layton
2009-11-10 16:27 ` [PATCH 1/2] vfs: force reval of dentries for LAST_BIND symlinks on open Jeff Layton
2009-11-10 16:27 ` [PATCH 2/2] vfs: force reval on dentry of bind mounted files for LOOKUP_OPEN Jeff Layton
2009-11-11 7:57 ` [PATCH 0/2] vfs: ensure that dentries are revalidated on open (try #2) Miklos Szeredi
2009-11-11 8:26 ` Trond Myklebust
2009-11-11 8:33 ` Miklos Szeredi
2009-11-11 12:17 ` Trond Myklebust [this message]
2009-11-11 12:36 ` Jeff Layton
2009-11-18 4:19 ` Pavel Machek
2009-11-18 12:29 ` Jeff Layton
2009-11-18 17:38 ` Pavel Machek
2009-11-18 18:54 ` Jeff Layton
2009-11-18 19:33 ` Pavel Machek
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=1257941839.2949.9.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=adobriyan@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jamie@shareable.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.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
all inboxes | Powered by JetHome®