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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 13 Feb 2014 21:55:33 +0000 (13:55 -0800)
commitf1e432ef9b915522fe16467221d86254ba6f9b5e
tree38de7b6ad4f4a5f36bdea5ce493423acb6f44d58
parent61b287aa886fa8c81b711eaca85e7f72ca37b9f7
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfs/nfs4proc.c