From: Steve Dickson <SteveD@redhat.com>
To: andros@netapp.com, trond.myklebust@primarydata.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] NFS: Fix SECINFO processing regression
Date: Tue, 10 Jun 2014 11:04:08 -0400 [thread overview]
Message-ID: <53971E68.3060200@RedHat.com> (raw)
In-Reply-To: <1402342401-5640-1-git-send-email-andros@netapp.com>
On 06/09/2014 03:33 PM, andros@netapp.com wrote:
> From: Andy Adamson <andros@netapp.com>
>
> Iterate over multiple flavors returned by SECINFO. If RPC_AUTH_GSS is in the
> secinfo list, fully test (get and auth, credential, and gss_context)
>
> Fix some error paths.
>
> Testing: Minimal testing of the nfs_test_gss_flavor. Will run more tests after
> the June 2014 bakeathon
>
> Note: Can supply a patch for SECINFO_NO_name to use nfs4_negotiate_security.
>
> Andy Adamson (3):
> NFS check the return of nfs4_negotiate_security in nfs4_submount
> NFS Return -EPERM if no supported or matching SECINFO flavor
> NFS test SECINFO RPC_AUTH_GSS pseudoflavors for support
>
> fs/nfs/nfs4namespace.c | 66 +++++++++++++++++++++++++++++++++++++++++---------
> 1 file changed, 55 insertions(+), 11 deletions(-)
>
Tested-By: Steve Dickson <steved@redhat.com>
next prev parent reply other threads:[~2014-06-10 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 19:33 [PATCH 0/3] NFS: Fix SECINFO processing regression andros
2014-06-09 19:33 ` [PATCH 1/3] NFS check the return of nfs4_negotiate_security in nfs4_submount andros
2014-06-09 19:33 ` [PATCH 2/3] NFS Return -EPERM if no supported or matching SECINFO flavor andros
2014-06-09 19:33 ` [PATCH 3/3] NFS test SECINFO RPC_AUTH_GSS pseudoflavors for support andros
2014-06-10 16:21 ` Trond Myklebust
2014-06-10 18:38 ` Adamson, Andy
2014-06-10 19:29 ` Trond Myklebust
2014-06-10 19:37 ` Adamson, Andy
2014-06-10 15:04 ` Steve Dickson [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-12 18:55 [PATCH 0/3] NFS: Fix SECINFO processing regression andros
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=53971E68.3060200@RedHat.com \
--to=steved@redhat.com \
--cc=andros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).