From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, Jan Stancek <jstancek@redhat.com>
Subject: Re: [PATCH v3] SUNRPC: Ensure that the RPCSEC_GSS daemon uses the correct service names
Date: Mon, 26 Aug 2013 13:11:19 -0400 [thread overview]
Message-ID: <20130826171119.GA13212@fieldses.org> (raw)
In-Reply-To: <20130824124314.GD18084@fieldses.org>
On Sat, Aug 24, 2013 at 08:43:14AM -0400, J. Bruce Fields wrote:
> On Fri, Aug 23, 2013 at 07:18:43PM -0400, J. Bruce Fields wrote:
> > On Thu, Aug 22, 2013 at 04:10:13PM -0400, Jeff Layton wrote:
> > > From: Trond Myklebust <Trond.Myklebust@netapp.com>
> > >
> > > v2: added pipe_dir_name field to nfsacl program to fix v3+krb5
> > > (Should we add pipe_dir_name fields to other programs too?).
> > >
> > > v3: Drop changes to gss_encode_v1_msg. They don't seem to be
> > > needed since gssd scrapes that out of the "info" file.
> >
> > Hm. nfsv3/krb5 is still broken for me after this patch. I'll try to
> > figure out why....
>
> Whoops, never mind, my client was booted to the wrong kernel, with this
> patch it does work.
Oh, and by the way, I made the same mistake testing Jan's original patch
(installed the patched kernel to the server but not the client...).
Retesting, it worked fine too.
--b.
next prev parent reply other threads:[~2013-08-26 17:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:10 [PATCH v3] SUNRPC: Ensure that the RPCSEC_GSS daemon uses the correct service names Jeff Layton
2013-08-23 23:18 ` J. Bruce Fields
2013-08-24 12:43 ` J. Bruce Fields
2013-08-24 14:30 ` Jeff Layton
2013-08-26 17:11 ` J. Bruce Fields [this message]
2013-08-24 4:56 ` Simo Sorce
2013-08-24 10:57 ` Jeff Layton
2013-08-24 12:42 ` J. Bruce Fields
2013-08-26 16:50 ` J. Bruce Fields
2013-08-26 21:28 ` J. Bruce Fields
2013-09-04 3:11 ` Simo Sorce
2013-09-04 13:39 ` J. Bruce Fields
2013-09-04 17:21 ` Simo Sorce
2013-09-04 17:49 ` J. Bruce Fields
2013-09-04 18:00 ` 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=20130826171119.GA13212@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=jlayton@redhat.com \
--cc=jstancek@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;
as well as URLs for NNTP newsgroup(s).