From: Jeff Layton <jlayton@redhat.com>
To: Joshua Watt <jpewhacker@gmail.com>, NeilBrown <neilb@suse.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
"J . Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC v4 4/9] namespace: Add umount_end superblock operation
Date: Wed, 06 Dec 2017 06:54:43 -0500 [thread overview]
Message-ID: <1512561283.4048.1.camel@redhat.com> (raw)
In-Reply-To: <20171117174552.18722-5-JPEWhacker@gmail.com>
On Fri, 2017-11-17 at 11:45 -0600, Joshua Watt wrote:
> The umount_end operation allows cleaning of state set by umount_begin in
> the event the filesystem doesn't actually get unmounted.
>
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> ---
> fs/namespace.c | 22 ++++++++++++++++++++--
> include/linux/fs.h | 1 +
> 2 files changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index d18deb4c410b..d2587be4d08b 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -1524,6 +1524,12 @@ static void umount_tree(struct mount *mnt, enum umount_tree_flags how)
> }
> }
>
> +static void umount_end(struct super_block *sb, int flags)
> +{
> + if (flags & MNT_FORCE && sb->s_op->umount_end)
nit: might get some complaints from compiler about order of operations
there. I'd put parenthesis around the flags & MNT_FORCE.
> + sb->s_op->umount_end(sb);
> +}
> +
> static void shrink_submounts(struct mount *mnt);
>
> static int do_umount(struct mount *mnt, int flags)
> @@ -1589,12 +1595,16 @@ static int do_umount(struct mount *mnt, int flags)
> * Special case for "unmounting" root ...
> * we just try to remount it readonly.
> */
> - if (!capable(CAP_SYS_ADMIN))
> - return -EPERM;
> + if (!capable(CAP_SYS_ADMIN)) {
> + retval = -EPERM;
> + goto out_umount_end;
> + }
> down_write(&sb->s_umount);
> if (!sb_rdonly(sb))
> retval = do_remount_sb(sb, SB_RDONLY, NULL, 0);
> up_write(&sb->s_umount);
> + /* Still mounted. Always invoke the cleanup */
> + umount_end(sb, flags);
> return retval;
> }
>
> @@ -1617,6 +1627,14 @@ static int do_umount(struct mount *mnt, int flags)
> }
> unlock_mount_hash();
> namespace_unlock();
> +
> +out_umount_end:
> + /* If the umount failed and the file system is still mounted, allow the
> + * driver to cleanup any state it may have setup in umount_begin(). Note
> + * that this is purposely *not* called when MNT_DETACH is specified.
> + */
> + if (retval)
> + umount_end(sb, flags);
> return retval;
> }
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 885266aae2d7..5443c22da18f 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -1816,6 +1816,7 @@ struct super_operations {
> int (*statfs) (struct dentry *, struct kstatfs *);
> int (*remount_fs) (struct super_block *, int *, char *);
> void (*umount_begin) (struct super_block *);
> + void (*umount_end)(struct super_block *);
>
> int (*show_options)(struct seq_file *, struct dentry *);
> int (*show_devname)(struct seq_file *, struct dentry *);
Since this involves vfs-level changes, please cc linux-fsdevel@vger.kern
el.org on further postings. Other filesystem devs may be interested in
what you're doing here.
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2017-12-06 11:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 17:45 [RFC v4 0/9] NFS Force Unmounting Joshua Watt
2017-11-17 17:45 ` [RFC v4 1/9] SUNRPC: Add flag to kill new tasks Joshua Watt
2017-12-05 22:59 ` NeilBrown
2017-11-17 17:45 ` [RFC v4 2/9] SUNRPC: Expose kill_new_tasks in debugfs Joshua Watt
2017-11-17 17:45 ` [RFC v4 3/9] SUNRPC: Simplify client shutdown Joshua Watt
2017-11-17 17:45 ` [RFC v4 4/9] namespace: Add umount_end superblock operation Joshua Watt
2017-12-06 11:54 ` Jeff Layton [this message]
2017-12-06 12:14 ` Al Viro
2017-12-06 12:33 ` Al Viro
2017-12-06 15:41 ` Joshua Watt
2017-11-17 17:45 ` [RFC v4 5/9] NFS: Kill RPCs for the duration of umount Joshua Watt
2017-12-05 23:07 ` NeilBrown
2017-11-17 17:45 ` [RFC v4 6/9] NFS: Add debugfs for nfs_server and nfs_client Joshua Watt
2017-11-17 17:45 ` [RFC v4 7/9] NFS: Add transient mount option Joshua Watt
2017-12-06 12:23 ` Jeff Layton
2017-11-17 17:45 ` [RFC v4 8/9] NFS: Don't shared transient clients Joshua Watt
2017-11-17 17:45 ` [RFC v4 9/9] NFS: Kill all client RPCs if transient Joshua Watt
2017-12-04 14:36 ` [RFC v4 0/9] NFS Force Unmounting Joshua Watt
2017-12-05 23:34 ` NeilBrown
2017-12-06 13:03 ` Jeff Layton
2017-12-06 16:40 ` Joshua Watt
2017-12-08 2:10 ` NeilBrown
2017-12-14 18:22 ` Joshua Watt
2017-12-14 21:52 ` NeilBrown
2017-12-18 21:48 ` Joshua Watt
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=1512561283.4048.1.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=dhowells@redhat.com \
--cc=jpewhacker@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--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).