All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NFS4 sec=krb5 broken in 3.9-rc8
Date: Fri, 26 Apr 2013 11:23:34 -0400	[thread overview]
Message-ID: <20130426152334.GC17268@fieldses.org> (raw)
In-Reply-To: <517A46E7.1020404@gmx.de>

On Fri, Apr 26, 2013 at 11:20:39AM +0200, Malte Schröder wrote:
> On 24.04.2013 21:23, J. Bruce Fields wrote:
> > On Wed, Apr 24, 2013 at 07:07:59PM +0200, Malte Schröder wrote:
> > Probably some of those "svc_process dropit"s are coming from attempts to
> > look up the newly created cred (so lookups in the rsc_cache) which fail
> > for some reason.  I'm not sure what that would be.
> > 
> > --b.
> 
> Hi,
> I tried bisecting the problem. It identified
> 683428fae8c73d7d7da0fa2e0b6beb4d8df4e808 as the problem, reverting it
> didn't fix the problem, though. During the process there where some
> states where mounting wouldn't hang but be denied. I will try bisecting
> again, later.

Oh, so probably 3c34ae11fac3b30629581d0bfaf80f58e82cfbfb "nfsd: fix krb5
handling of anonymous principals" needs backporting to stable--could you
confirm whether applying that helps?

Thanks for the bisection.

--b.

  reply	other threads:[~2013-04-26 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 19:55 NFS4 sec=krb5 broken in 3.9-rc8 Malte Schröder
2013-04-23 21:58 ` J. Bruce Fields
2013-04-24  5:58   ` Malte Schröder
2013-04-24 14:01     ` J. Bruce Fields
2013-04-24 17:07       ` Malte Schröder
2013-04-24 19:23         ` J. Bruce Fields
2013-04-26  9:20           ` Malte Schröder
2013-04-26 15:23             ` J. Bruce Fields [this message]
2013-04-26 16:56               ` Malte Schröder
2013-04-26 17:16                 ` 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=20130426152334.GC17268@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=maltesch@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.