Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 97431204 authored by Andy Adamson's avatar Andy Adamson Committed by Trond Myklebust
Browse files

NFSv4.1 Use clientid management rpc_clnt for secinfo_no_name 



As per RFC 5661 Security Considerations

Commit 4edaa308 "NFS: Use "krb5i" to establish NFSv4 state whenever possible"
uses the nfs_client cl_rpcclient for all clientid management operations.

Signed-off-by: default avatarAndy Adamson <andros@netapp.com>
Signed-off-by: default avatarTrond Myklebust <Trond.Myklebust@netapp.com>
parent 5ec16a85

fs/nfs/nfs4proc.c

+6 −1
Original line number Diff line number Diff line
@@ -7090,6 +7090,10 @@ nfs4_proc_layoutcommit(struct nfs4_layoutcommit_data *data, bool sync) 
	return status;

}



/**

 * Use the state managment nfs_client cl_rpcclient, which uses krb5i (if

 * possible) as per RFC3530bis and RFC5661 Security Considerations sections

 */

static int

_nfs41_proc_secinfo_no_name(struct nfs_server *server, struct nfs_fh *fhandle,

		    struct nfs_fsinfo *info, struct nfs4_secinfo_flavors *flavors)
@@ -7105,7 +7109,8 @@ _nfs41_proc_secinfo_no_name(struct nfs_server *server, struct nfs_fh *fhandle, 
		.rpc_argp = &args,

		.rpc_resp = &res,

	};

	return nfs4_call_sync(server->client, server, &msg, &args.seq_args, &res.seq_res, 0);

	return nfs4_call_sync(server->nfs_client->cl_rpcclient, server, &msg,

				&args.seq_args, &res.seq_res, 0);

}



static int