From: Joshua Watt <jpewhacker@gmail.com>
To: NeilBrown <neilb@suse.com>, Jeff Layton <jlayton@redhat.com>,
Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
"J . Bruce Fields" <bfields@fieldses.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC 4/4] NFS: Add forcekill mount option
Date: Fri, 10 Nov 2017 08:16:56 -0600 [thread overview]
Message-ID: <1510323416.2495.28.camel@gmail.com> (raw)
In-Reply-To: <87fu9mevtq.fsf@notabene.neil.brown.name>
On Fri, 2017-11-10 at 13:01 +1100, NeilBrown wrote:
> On Wed, Nov 08 2017, Joshua Watt wrote:
>
> > Specifying the forcekill mount option causes umount() with the
> > MNT_FORCE
> > flag to not only kill all currently pending RPC tasks with -EIO,
> > but
> > also all future RPC tasks. This prevents the long delays caused by
> > tasks
> > queuing after rpc_killall_tasks() that can occur if the server
> > drops off
> > the network.
> >
> > Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> > ---
> > fs/nfs/super.c | 17 ++++++++++++++---
> > include/uapi/linux/nfs_mount.h | 1 +
> > 2 files changed, 15 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> > index 66fda2dcadd0..d972f6289aca 100644
> > --- a/fs/nfs/super.c
> > +++ b/fs/nfs/super.c
> > @@ -90,6 +90,7 @@ enum {
> > Opt_resvport, Opt_noresvport,
> > Opt_fscache, Opt_nofscache,
> > Opt_migration, Opt_nomigration,
> > + Opt_forcekill, Opt_noforcekill,
> >
> > /* Mount options that take integer arguments */
> > Opt_port,
> > @@ -151,6 +152,8 @@ static const match_table_t
> > nfs_mount_option_tokens = {
> > { Opt_nofscache, "nofsc" },
> > { Opt_migration, "migration" },
> > { Opt_nomigration, "nomigration" },
> > + { Opt_forcekill, "forcekill" },
> > + { Opt_noforcekill, "noforcekill" },
> >
> > { Opt_port, "port=%s" },
> > { Opt_rsize, "rsize=%s" },
> > @@ -637,6 +640,7 @@ static void nfs_show_mount_options(struct
> > seq_file *m, struct nfs_server *nfss,
> > { NFS_MOUNT_NORDIRPLUS, ",nordirplus", "" },
> > { NFS_MOUNT_UNSHARED, ",nosharecache", "" },
> > { NFS_MOUNT_NORESVPORT, ",noresvport", "" },
> > + { NFS_MOUNT_FORCEKILL, ",forcekill",
> > ",noforcekill" },
> > { 0, NULL, NULL }
> > };
> > const struct proc_nfs_info *nfs_infop;
> > @@ -896,17 +900,18 @@ EXPORT_SYMBOL_GPL(nfs_show_stats);
> > */
> > void nfs_umount_begin(struct super_block *sb)
> > {
> > - struct nfs_server *server;
> > + struct nfs_server *server = NFS_SB(sb);
> > struct rpc_clnt *rpc;
> > + int kill_new_tasks = !!(server->flags &
> > NFS_MOUNT_FORCEKILL);
> >
> > server = NFS_SB(sb);
>
> Now that you initialized 'server' at declaration, you should really
> remove this (re)initialization.
Oops.
>
> I'm not sure what I think of this patchset...
> You are setting a flag which causes "umount -f" to set a different
> flag.
> Why not just have "mount -o remount,XX" set the flag that you
> actually
> want to set.
> e.g
> mount -o remount,serverfailed /mountpoint
> causes all rpcs to fail, and
> mount -o remount,noserverfailed /mountpoint
>
> causes all rpcs to be sent to the server.
> (or pick a different name than 'serverfailed').
Ah. I think I get it now :) Yes I will do that.
>
> It isn't clear what the indirection buys us.
>
> Thanks,
> NeilBrown
>
>
>
> > /* -EIO all pending I/O */
> > rpc = server->client_acl;
> > if (!IS_ERR(rpc))
> > - rpc_killall_tasks(rpc, 0);
> > + rpc_killall_tasks(rpc, kill_new_tasks);
> > rpc = server->client;
> > if (!IS_ERR(rpc))
> > - rpc_killall_tasks(rpc, 0);
> > + rpc_killall_tasks(rpc, kill_new_tasks);
> > }
> > EXPORT_SYMBOL_GPL(nfs_umount_begin);
> >
> > @@ -1334,6 +1339,12 @@ static int nfs_parse_mount_options(char
> > *raw,
> > case Opt_nomigration:
> > mnt->options &= ~NFS_OPTION_MIGRATION;
> > break;
> > + case Opt_forcekill:
> > + mnt->flags |= NFS_MOUNT_FORCEKILL;
> > + break;
> > + case Opt_noforcekill:
> > + mnt->flags &= ~NFS_MOUNT_FORCEKILL;
> > + break;
> >
> > /*
> > * options that take numeric values
> > diff --git a/include/uapi/linux/nfs_mount.h
> > b/include/uapi/linux/nfs_mount.h
> > index e44e00616ab5..66821542a38f 100644
> > --- a/include/uapi/linux/nfs_mount.h
> > +++ b/include/uapi/linux/nfs_mount.h
> > @@ -74,5 +74,6 @@ struct nfs_mount_data {
> >
> > #define NFS_MOUNT_LOCAL_FLOCK 0x100000
> > #define NFS_MOUNT_LOCAL_FCNTL 0x200000
> > +#define NFS_MOUNT_FORCEKILL 0x400000
> >
> > #endif
> > --
> > 2.13.6
prev parent reply other threads:[~2017-11-10 14:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 17:11 NFS Force Unmounting Joshua Watt
2017-10-30 20:20 ` J. Bruce Fields
2017-10-30 21:04 ` Joshua Watt
2017-10-30 21:09 ` NeilBrown
2017-10-31 14:41 ` Jeff Layton
2017-10-31 14:55 ` Chuck Lever
2017-10-31 17:04 ` Joshua Watt
2017-10-31 19:46 ` Chuck Lever
2017-11-01 0:53 ` NeilBrown
2017-11-01 2:22 ` Chuck Lever
2017-11-01 14:38 ` Joshua Watt
2017-11-02 0:15 ` NeilBrown
2017-11-02 19:46 ` Chuck Lever
2017-11-02 21:51 ` NeilBrown
2017-11-01 17:24 ` Jeff Layton
2017-11-01 23:13 ` NeilBrown
2017-11-02 12:09 ` Jeff Layton
2017-11-02 14:54 ` Joshua Watt
2017-11-08 3:30 ` NeilBrown
2017-11-08 12:08 ` Jeff Layton
2017-11-08 15:52 ` J. Bruce Fields
2017-11-08 22:34 ` NeilBrown
2017-11-08 23:52 ` Trond Myklebust
2017-11-09 19:48 ` Joshua Watt
2017-11-10 0:16 ` NeilBrown
2017-11-08 14:59 ` [RFC 0/4] " Joshua Watt
2017-11-08 14:59 ` [RFC 1/4] SUNRPC: Add flag to kill new tasks Joshua Watt
2017-11-10 1:39 ` NeilBrown
2017-11-08 14:59 ` [RFC 2/4] SUNRPC: Kill client tasks from debugfs Joshua Watt
2017-11-10 1:47 ` NeilBrown
2017-11-10 14:13 ` Joshua Watt
2017-11-08 14:59 ` [RFC 3/4] SUNRPC: Simplify client shutdown Joshua Watt
2017-11-10 1:50 ` NeilBrown
2017-11-08 14:59 ` [RFC 4/4] NFS: Add forcekill mount option Joshua Watt
2017-11-10 2:01 ` NeilBrown
2017-11-10 14:16 ` Joshua Watt [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=1510323416.2495.28.camel@gmail.com \
--to=jpewhacker@gmail.com \
--cc=bfields@fieldses.org \
--cc=dhowells@redhat.com \
--cc=jlayton@redhat.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).