NFS: Add SECINFO_NO_NAME procedure
If the client is using NFS v4.1, then we can use SECINFO_NO_NAME to find the secflavor for the initial mount. If the server doesn't support SECINFO_NO_NAME then I fall back on the "guess and check" method used for v4.0 mounts. Signed-off-by: Bryan Schumaker <bjschuma@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
This commit is contained in:

committed by
Trond Myklebust

parent
6382a44138
commit
fca78d6d2c
@@ -1084,6 +1084,14 @@ struct nfs41_reclaim_complete_args {
|
||||
struct nfs41_reclaim_complete_res {
|
||||
struct nfs4_sequence_res seq_res;
|
||||
};
|
||||
|
||||
#define SECINFO_STYLE_CURRENT_FH 0
|
||||
#define SECINFO_STYLE_PARENT 1
|
||||
struct nfs41_secinfo_no_name_args {
|
||||
int style;
|
||||
struct nfs4_sequence_args seq_args;
|
||||
};
|
||||
|
||||
#endif /* CONFIG_NFS_V4_1 */
|
||||
|
||||
struct nfs_page;
|
||||
|
Reference in New Issue
Block a user