tree 5378bd6ad0917cf11ad7f7b739b71794df230c85
parent 6382a44138e7aa40bf52170e7afc014443a24806
author Bryan Schumaker <bjschuma@netapp.com> 1307041147 -0400
committer Trond Myklebust <Trond.Myklebust@netapp.com> 1310492427 -0400

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>