public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Miklos Szeredi <mszeredi@suse.cz>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Ric Wheeler <rwheeler@redhat.com>, Anand Avati <avati@redhat.com>,
	Brian Foster <bfoster@redhat.com>,
	David Howells <dhowells@redhat.com>,
	Eric Paris <eparis@redhat.com>,
	Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	KONISHI Ryusuke <konishi.ryusuke@lab.ntt.co.jp>
Subject: Re: [PATCH 0/9] [RFC v2] safely drop directory dentry on failed revalidate
Date: Sun, 01 Sep 2013 09:00:29 +0800	[thread overview]
Message-ID: <1377997229.4223.9.camel@perseus.fritz.box> (raw)
In-Reply-To: <1377996985.4223.6.camel@perseus.fritz.box>

On Sun, 2013-09-01 at 08:56 +0800, Ian Kent wrote:
> On Fri, 2013-08-30 at 10:59 +0200, Miklos Szeredi wrote:
> > On Fri, Aug 30, 2013 at 1:44 AM, Ian Kent <raven@themaw.net> wrote:
> > 
> > >> The check in waitq.c above "is" used to validate the need to callback to
> > >> the daemon to request a mount.
> > 
> > Okay.  But then shouldn't the check be  "if (d_mountpoint(dentry)) valid = 0;" ?
> 
> I don't think so.
> 
> But again, may_umount() might do what's needed here too.

Oh, hang on, may_umount() can't be used for the root-less multi-mount
case at all, since there's no vfsmount at the base of the tree the check
can't be restricted to just the tree of subdirs that needs to be
checked. That's been a problem for me for a long time.

> 
> I don't think this is enough because it doesn't cover the case where the
> dentry is not simple_empty() but has no mounts below. That's not a
> normal use case but could happen if the daemon crashed at just the wrong
> time, encountered an error condition that didn't allow it to cleanup
> directories, or a user umounted triggers within the tree before starting
> the daemon.
> 
> > 
> > Thanks,
> > Miklos
> 



      reply	other threads:[~2013-09-01  1:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 15:24 [PATCH 0/9] [RFC v2] safely drop directory dentry on failed revalidate Miklos Szeredi
2013-08-08 15:24 ` [PATCH 1/9] vfs: check submounts and drop atomically Miklos Szeredi
2013-08-12 13:27   ` Jeff Layton
2013-08-08 15:24 ` [PATCH 2/9] vfs: check unlinked ancestors before mount Miklos Szeredi
2013-08-12 13:33   ` Jeff Layton
2013-08-08 15:24 ` [PATCH 3/9] afs: use check_submounts_and_drop() Miklos Szeredi
2013-08-08 15:24 ` [PATCH 4/9] gfs2: " Miklos Szeredi
2013-08-08 15:24 ` [PATCH 5/9] nfs: " Miklos Szeredi
2013-08-12 13:34   ` Jeff Layton
2013-08-08 15:24 ` [PATCH 6/9] sysfs: " Miklos Szeredi
2013-08-08 15:24 ` [PATCH 7/9] fuse: use d_materialise_unique() Miklos Szeredi
2013-08-08 15:24 ` [PATCH 8/9] fuse: clean up return in fuse_dentry_revalidate() Miklos Szeredi
2013-08-08 15:24 ` [PATCH 9/9] fuse: drop dentry on failed revalidate Miklos Szeredi
2013-08-21  5:40 ` [PATCH 0/9] [RFC v2] safely drop directory " Al Viro
2013-08-21 20:04   ` Ryusuke Konishi
2013-08-21 21:00     ` Al Viro
2013-08-21 23:47       ` Ryusuke Konishi
2013-08-29  3:51   ` Miklos Szeredi
2013-08-29 23:24     ` Ian Kent
2013-08-29 23:44       ` Ian Kent
2013-08-30  8:59         ` Miklos Szeredi
2013-09-01  0:56           ` Ian Kent
2013-09-01  1:00             ` Ian Kent [this message]

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=1377997229.4223.9.camel@perseus.fritz.box \
    --to=raven@themaw.net \
    --cc=avati@redhat.com \
    --cc=bfoster@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=eparis@redhat.com \
    --cc=konishi.ryusuke@lab.ntt.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@suse.cz \
    --cc=rwheeler@redhat.com \
    --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