From: Boaz Harrosh <bharrosh@panasas.com>
To: Weston Andros Adamson <dros@primarydata.com>
Cc: <trond.myklebust@primarydata.com>, <linux-nfs@vger.kernel.org>,
Ganesha NFS List <nfs-ganesha-devel@lists.sourceforge.net>
Subject: Re: [PATCH] nfs4.1: properly handle ENOTSUP in SECINFO_NO_NAME
Date: Tue, 14 Jan 2014 17:22:23 +0200 [thread overview]
Message-ID: <52D5562F.70701@panasas.com> (raw)
In-Reply-To: <1389650085-4128-1-git-send-email-dros@primarydata.com>
On 01/13/2014 11:54 PM, Weston Andros Adamson wrote:
> 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>
> ---
>
> I found this trying to mount a pynfs filelayout server.
>
Yes at last BAT Frank fixed Ganesha so it can work with new clients.
Linux client is the standard the rest of the world needs to comply
(Resistance is futile ;-) )
Thanks
Boaz
> fs/nfs/nfs4proc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index 15052b8..1d57b6a 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -7920,7 +7920,7 @@ nfs41_proc_secinfo_no_name(struct nfs_server *server, struct nfs_fh *fhandle,
> switch (err) {
> case 0:
> case -NFS4ERR_WRONGSEC:
> - case -NFS4ERR_NOTSUPP:
> + case -ENOTSUPP:
> goto out;
> default:
> err = nfs4_handle_exception(server, err, &exception);
> @@ -7954,7 +7954,7 @@ nfs41_find_root_sec(struct nfs_server *server, struct nfs_fh *fhandle,
> * Fall back on "guess and check" method if
> * the server doesn't support SECINFO_NO_NAME
> */
> - if (err == -NFS4ERR_WRONGSEC || err == -NFS4ERR_NOTSUPP) {
> + if (err == -NFS4ERR_WRONGSEC || err == -ENOTSUPP) {
> err = nfs4_find_root_sec(server, fhandle, info);
> goto out_freepage;
> }
>
prev parent reply other threads:[~2014-01-14 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 21:54 [PATCH] nfs4.1: properly handle ENOTSUP in SECINFO_NO_NAME Weston Andros Adamson
2014-01-14 15:22 ` Boaz Harrosh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D5562F.70701@panasas.com \
--to=bharrosh@panasas.com \
--cc=dros@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfs-ganesha-devel@lists.sourceforge.net \
--cc=trond.myklebust@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox