From: "J. Bruce Fields" <bfields@fieldses.org>
To: Simo Sorce <simo@redhat.com>
Cc: Scott Mayhew <smayhew@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures
Date: Wed, 29 Apr 2015 11:39:22 -0400 [thread overview]
Message-ID: <20150429153922.GC18344@fieldses.org> (raw)
In-Reply-To: <20150429153834.GB18344@fieldses.org>
On Wed, Apr 29, 2015 at 11:38:34AM -0400, J. Bruce Fields wrote:
> On Tue, Apr 28, 2015 at 05:09:25PM -0400, Simo Sorce wrote:
> > Thanks Scott,
> > I think this will help with older GSS-Proxy versions, in the newer
> > versions we are simply suppressing the exported composite name as the
> > kernel has no use for it.
>
> Thanks. (Also adding a Reviewed-by: Simo Sorce <simo@redhat.com>.)
(And a stable cc:.)
--b.
prev parent reply other threads:[~2015-04-29 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 20:29 [PATCH] svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures Scott Mayhew
2015-04-28 21:09 ` Simo Sorce
2015-04-29 15:38 ` J. Bruce Fields
2015-04-29 15:39 ` J. Bruce Fields [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=20150429153922.GC18344@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=simo@redhat.com \
--cc=smayhew@redhat.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).