From: Jeff Layton <jlayton@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Jan Stancek <jstancek@redhat.com>,
linux-nfs@vger.kernel.org, bfields@redhat.com,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [PATCH] NFS: fix NFSv3 with sec=krb5 and CONFIG_NFS_V3_ACL=y
Date: Thu, 15 Aug 2013 10:02:44 -0400 [thread overview]
Message-ID: <20130815100244.370de645@corrin.poochiereds.net> (raw)
In-Reply-To: <20130726220924.GG30651@fieldses.org>
On Fri, 26 Jul 2013 18:09:24 -0400
"J. Bruce Fields" <bfields@fieldses.org> wrote:
> On Tue, Jul 09, 2013 at 02:59:54AM -0400, Jan Stancek wrote:
> >
> >
> >
> >
> > ----- Original Message -----
> > > From: "J. Bruce Fields" <bfields@fieldses.org>
> > > To: "Jan Stancek" <jstancek@redhat.com>
> > > Cc: linux-nfs@vger.kernel.org, bfields@redhat.com, "Trond Myklebust" <Trond.Myklebust@netapp.com>
> > > Sent: Monday, 8 July, 2013 10:16:43 PM
> > > Subject: Re: [PATCH] NFS: fix NFSv3 with sec=krb5 and CONFIG_NFS_V3_ACL=y
> > >
> > > On Mon, Jul 01, 2013 at 05:32:34PM +0200, Jan Stancek wrote:
> > > > Starting with commit:
> > > > commit f994c43d19a9116727d4c228d3f13db595bff562
> > > > Author: Trond Myklebust <Trond.Myklebust@netapp.com>
> > > > Date: Thu Nov 1 12:14:14 2012 -0400
> > > > SUNRPC: Clean up rpc_bind_new_program
> > > >
> > > > operations on directory mounted with -onfsvers=3,tcp,sec=krb5 fail
> > > > with Input/Output error after ~60 second timeout. This is presumably
> > > > because upcalls for 'nfsacl' are not getting anywhere.
> > > >
> > > > This patch enables pipe dir for nfsacl_program and changes its name
> > > > to 'nfs'. This name will be used in upcalls and whole setup should
> > > > work as it did in past - just with nfs/hostname principal.
> > >
> > > I think this was the problem that nfs-utils commits
> > >
> > > a1f8afc560 gssd: Remove insane sanity checks of the service name
> > > a56989b665 gssd: Handle the target name correctly
> > >
> > > were supposed to fix?
> > >
> > > But perhaps the kernel needs a fix too to fix a regression with old
> > > userspace.
> >
> > I saw this error with nfs-utils.1.2.9-rc1, which should already contain
> > those 2 commits.
>
> Actually, I think your patch is just a subset of Trond's
> http://mid.gmane.org/<4FA345DA4F4AE44899BD2B03EEEC2FA9092EC392@SACEXCMBX04-PRD.hq.netapp.com>
>
> Trond, is there a reason that never got applied?
>
> --b.
>
Hmm...gmane just says "No such article" when I feed it the above URL.
Do you know what the title of the email was?
Thanks,
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2013-08-15 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 15:32 [PATCH] NFS: fix NFSv3 with sec=krb5 and CONFIG_NFS_V3_ACL=y Jan Stancek
2013-07-08 20:16 ` J. Bruce Fields
2013-07-09 6:59 ` Jan Stancek
2013-07-26 22:09 ` J. Bruce Fields
2013-08-15 14:02 ` Jeff Layton [this message]
2013-08-15 14:19 ` J. Bruce Fields
2013-08-16 19:04 ` Jeff Layton
2013-08-16 19:16 ` J. Bruce Fields
2013-08-16 20:40 ` Jeff Layton
2013-08-19 12:06 ` Jeff Layton
2013-08-19 12:36 ` simo
2013-08-19 13:15 ` 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=20130815100244.370de645@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=bfields@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).