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: Andy Adamson <andros@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
This commit is contained in:
parent
5ec16a8500
commit
97431204ea
@ -7090,6 +7090,10 @@ out:
|
||||
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
|
||||
|
Loading…
Reference in New Issue
Block a user