nfs4.1: properly handle ENOTSUP in SECINFO_NO_NAME
authorWeston Andros Adamson <dros@primarydata.com>
Mon, 13 Jan 2014 21:54:45 +0000 (16:54 -0500)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 1 Apr 2014 23:58:43 +0000 (00:58 +0100)
commitb2cf3f5e629ff7424e683197e849f598be53a11c
treeff5da4d7d3a989ac4750e283aa4dafb034b6549c
parentc9d051d0b5bc88d36a53ac5724301b26a7c1bf1c
nfs4.1: properly handle ENOTSUP in SECINFO_NO_NAME

commit 78b19bae0813bd6f921ca58490196abd101297bd upstream.

Don't check for -NFS4ERR_NOTSUPP, it's already been mapped to -ENOTSUPP
by nfs4_stat_to_errno.

This allows the client to mount v4.1 servers that don't support
SECINFO_NO_NAME by falling back to the "guess and check" method of
nfs4_find_root_sec.

Signed-off-by: Weston Andros Adamson <dros@primarydata.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/nfs/nfs4proc.c