[3/5] pNFS: nfs3_set_ds_client should set NFS_CS_NOPING
diff mbox series

Message ID 20191017173548.105111-3-trond.myklebust@hammerspace.com
State New
Headers show
  • [1/5] NFS: Use non-atomic bit ops when initialising struct nfs_client_initdata
Related show

Commit Message

Trond Myklebust Oct. 17, 2019, 5:35 p.m. UTC
Connecting to the DS is a non-interactive, asynchronous task, so there is
no reason to fire up an extra RPC null ping in order to ensure that the
server is up.

Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
 fs/nfs/nfs3client.c | 2 ++
 1 file changed, 2 insertions(+)

diff mbox series

diff --git a/fs/nfs/nfs3client.c b/fs/nfs/nfs3client.c
index 178dc102442f..793fa4273edb 100644
--- a/fs/nfs/nfs3client.c
+++ b/fs/nfs/nfs3client.c
@@ -108,6 +108,8 @@  struct nfs_client *nfs3_set_ds_client(struct nfs_server *mds_srv,
 	if (mds_srv->flags & NFS_MOUNT_NORESVPORT)
 		__set_bit(NFS_CS_NORESVPORT, &cl_init.init_flags);
+	__set_bit(NFS_CS_NOPING, &cl_init.init_flags);
 	/* Use the MDS nfs_client cl_ipaddr. */
 	nfs_init_timeout_values(&ds_timeout, ds_proto, ds_timeo, ds_retrans);
 	clp = nfs_get_client(&cl_init);