From: NeilBrown <neilb@suse.com>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: [PATCH 4/6 v9] fs: New helper legitimize_mntget() for getting a legitimize mnt
Date: Wed, 19 Aug 2015 14:56:50 +1000 [thread overview]
Message-ID: <20150819145650.46352023@noble> (raw)
In-Reply-To: <55D2DD17.7050504@gmail.com>
On Tue, 18 Aug 2015 15:21:59 +0800 Kinglong Mee <kinglongmee@gmail.com>
wrote:
> New helper legitimize_mntget for getting a mnt without setting
> MNT_SYNC_UMOUNT | MNT_UMOUNT | MNT_DOOMED, otherwise return NULL.
>
> v9, Update using read_seqbegin_or_lock instead read_seqlock_excl
>
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> ---
> fs/namespace.c | 30 ++++++++++++++++++++++++++++++
> include/linux/mount.h | 1 +
> 2 files changed, 31 insertions(+)
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index 2b8aa15..bf4a9f5 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -1153,6 +1153,36 @@ struct vfsmount *mntget(struct vfsmount *mnt)
> }
> EXPORT_SYMBOL(mntget);
>
> +struct vfsmount *legitimize_mntget(struct vfsmount *vfsmnt)
> +{
> + struct mount *mnt;
> + unsigned seq = 0;
> +
> + if (vfsmnt == NULL)
> + return NULL;
> +retry:
> + read_seqbegin_or_lock(&mount_lock, &seq);
> +
> + if (vfsmnt->mnt_flags & (MNT_SYNC_UMOUNT | MNT_UMOUNT | MNT_DOOMED))
> + vfsmnt = NULL;
> + else if (need_seqretry(&mount_lock, seq))
> + goto retry;
> + else {
> + mnt = real_mount(vfsmnt);
> + mnt_add_count(mnt, 1);
> + if (need_seqretry(&mount_lock, seq) ||
> + vfsmnt->mnt_flags & (MNT_SYNC_UMOUNT | MNT_UMOUNT |
> + MNT_DOOMED)) {
> + mnt_add_count(mnt, -1);
> + goto retry;
> + }
> + }
> +
> + done_seqretry(&mount_lock, seq);
> + return vfsmnt;
> +}
> +EXPORT_SYMBOL(legitimize_mntget);
I'm struggling with this. I know I wrote the above, but I'm no longer
sure it is correct .. at all.
All three of those flags are only set while mount_lock is held for
writing, so if the second need_seqretry() returns zero, then we can
be certain that none of the flags have changed yet, so there is no point
testing them again.
Ahh... looking back at __legitimize_mnt I think I see the important
point now - or at least I now see that point which I saw before more
clearly.
After the mnt_add_count, if need_seqretry() returns zero, we are done.
If not, we need to clean up and try again.
To do this we need to check MNT_SYNC_UMOUNT.
If that is clear it is safe and best to call mntput() on the mnt.
If it is set, then we just do the mnt_add_count(mnt, -1) and give up
completely.
Also, the usage for read_seqbegin_or_lock is all wrong. I'm sure I
copied something but I got it badly wrong.
When you retry, you need to set 'seq' to 1, otherwise it never locks.
I thought it would be more "clever" than at.
So maybe:
retry:
read_seqbegin_or_lock(&mount_lock, &seq);
if (vfsmnt->mnt_flags & (....))
vfs_mnt = NULL;
else {
mnt = real_mount(vfsmnt);
mnt_add_count(mnt, 1);
if (need_seqretry(&mount_lock, seq)) {
/* lost the race, need to try again */
if (vfsmnt->mnt_flags & MNT_SYNC_UMOUNT) {
/* no point trying... */
mnt_add_count(mnt, -1):
vfsmnt = NULL;
} else {
mntput(vfsmnt);
seq = 1;
goto retry;
}
}
}
done_seqretry(&mount_lock, seq);
return vfsmnt;
NeilBrown
next prev parent reply other threads:[~2015-08-19 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 7:17 [PATCH 0/6 v9] NFSD: Pin to vfsmount for nfsd exports cache Kinglong Mee
2015-08-18 7:18 ` [PATCH 1/6 v9] fs-pin: allow pin_remove() to be called other than from->kill() Kinglong Mee
2015-08-18 7:19 ` [PATCH 2/6] fs_pin: Export functions for specific filesystem Kinglong Mee
2015-08-18 7:20 ` [PATCH 3/6 v9] path: New helpers path_get_pin/path_put_unpin for path pin Kinglong Mee
2015-08-18 7:21 ` [PATCH 4/6 v9] fs: New helper legitimize_mntget() for getting a legitimize mnt Kinglong Mee
2015-08-19 4:56 ` NeilBrown [this message]
2015-08-19 5:02 ` Al Viro
2015-08-27 23:02 ` Kinglong Mee
2015-08-18 7:22 ` [PATCH 5/6 v9] sunrpc: New helper cache_delete_entry for deleting cache_head directly Kinglong Mee
2015-08-18 7:23 ` [PATCH 6/6 v9] nfsd: Allows user un-mounting filesystem where nfsd exports base on Kinglong Mee
2015-08-19 3:54 ` NeilBrown
2015-08-19 4:50 ` Al Viro
2015-08-27 23:15 ` Kinglong Mee
2015-08-18 7:24 ` [PATCH 2/6 v9] fs_pin: Export functions for specific filesystem Kinglong Mee
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=20150819145650.46352023@noble \
--to=neilb@suse.com \
--cc=bfields@fieldses.org \
--cc=kinglongmee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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;
as well as URLs for NNTP newsgroup(s).