linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: trond.myklebust@netapp.com
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfs: allow NFSv3 to fall back to AUTH_UNIX if initial auth selection fails
Date: Wed, 26 Jun 2013 10:36:01 -0400	[thread overview]
Message-ID: <1372257363-28148-1-git-send-email-jlayton@redhat.com> (raw)

I got a report of a regression in recent kernels. Windows 2012 servers
support v3 and v4.1. They also return a list of authflavors that starts
with AUTH_GSS flavors and ends with AUTH_SYS.

Since commit 4580a92 (NFS: Use server-recommended security flavor by
default (NFSv3)) mounting this server with nfsv3 fails unless you
specify sec=sys.

NFSv4.0 has code that allows it to fall back to using AUTH_SYS if the
initial attempt to use AUTH_GSS fails (in
nfs4_discover_server_trunking()). This is an attempt to make the v3
mounting code just as resilient in the same situation.

Jeff Layton (2):
  nfs: make nfs_select_flavor take a list of authflavors and a length
  nfs: allow NFSv3 to fall back to using AUTH_UNIX automatically if
    available

 fs/nfs/super.c | 51 +++++++++++++++++++++++++++++++++++++--------------
 1 file changed, 37 insertions(+), 14 deletions(-)

-- 
1.8.1.4


             reply	other threads:[~2013-06-26 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 14:36 Jeff Layton [this message]
2013-06-26 14:36 ` [PATCH 1/2] nfs: make nfs_select_flavor take a list of authflavors and a length Jeff Layton
2013-06-26 14:36 ` [PATCH 2/2] nfs: allow NFSv3 to fall back to using AUTH_UNIX automatically if available Jeff Layton
2013-06-26 15:15   ` Chuck Lever
2013-06-26 15:24     ` Jeff Layton
2013-06-26 15:37       ` Chuck Lever
2013-06-26 15:41         ` Jeff Layton
2013-06-26 15:29     ` Jeff Layton

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=1372257363-28148-1-git-send-email-jlayton@redhat.com \
    --to=jlayton@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.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;
as well as URLs for NNTP newsgroup(s).