Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@redhat.com>
To: linux-nfs@vger.kernel.org
Cc: "J. Bruce Fields" <bfields@redhat.com>
Subject: [PATCH 0/5] fix nfs server handling of principal names
Date: Tue, 24 Nov 2015 12:18:12 -0500	[thread overview]
Message-ID: <1448385497-23737-1-git-send-email-bfields@redhat.com> (raw)

From: "J. Bruce Fields" <bfields@redhat.com>

Thanks to James Ralston for helping debug a problem with the server's
handling of kerberos principal names, which could cause 4.1 mount
failures when using Active Directory.

Along the way I noticed another bug and some opportunities for minor
cleanup.

--b.

J. Bruce Fields (5):
  svcrpc: move some initialization to common code
  nfsd: helper for dup of possibly NULL string
  nfsd: minor consolidation of mach_cred handling code
  nfsd: fix unlikely NULL deref in mach_creds_match
  nfsd4: fix gss-proxy 4.1 mounts for some AD principals

 fs/nfsd/nfs4state.c                  | 55 +++++++++++++++++++++++++++---------
 include/linux/sunrpc/svcauth.h       |  9 +++++-
 net/sunrpc/auth_gss/gss_rpc_upcall.c |  3 ++
 net/sunrpc/svcauth.c                 |  2 ++
 net/sunrpc/svcauth_unix.c            |  8 ------
 5 files changed, 55 insertions(+), 22 deletions(-)

-- 
2.5.0


             reply	other threads:[~2015-11-24 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 17:18 J. Bruce Fields [this message]
2015-11-24 17:18 ` [PATCH 1/5] svcrpc: move some initialization to common code J. Bruce Fields
2015-11-24 17:18 ` [PATCH 2/5] nfsd: helper for dup of possibly NULL string J. Bruce Fields
2015-11-24 17:18 ` [PATCH 3/5] nfsd: minor consolidation of mach_cred handling code J. Bruce Fields
2015-11-24 17:18 ` [PATCH 4/5] nfsd: fix unlikely NULL deref in mach_creds_match J. Bruce Fields
2015-11-24 17:18 ` [PATCH 5/5] nfsd4: fix gss-proxy 4.1 mounts for some AD principals J. Bruce Fields
2015-11-24 18:05   ` Simo Sorce
2015-11-24 18:36     ` J. Bruce Fields

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=1448385497-23737-1-git-send-email-bfields@redhat.com \
    --to=bfields@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    /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