From: "J. Bruce Fields" <bfields@fieldses.org>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org
Subject: Re: krb5 failures in recent nfs-for-next
Date: Wed, 21 Mar 2012 15:45:44 -0400 [thread overview]
Message-ID: <20120321194544.GC11222@fieldses.org> (raw)
In-Reply-To: <4F6A2DE8.6060403@netapp.com>
On Wed, Mar 21, 2012 at 03:37:12PM -0400, Bryan Schumaker wrote:
> On 03/21/2012 03:24 PM, J. Bruce Fields wrote:
>
> > Have you been doing any krb5 testing?
>
>
> Not yet. It's still on my Jenkins todo list, but I haven't gotten around to it yet. Sounds like we need it, though, so I'll try working on it soon.
Actually, I've since seen the failure over nfsv4 and auth_sys. All
that's left on the console is enough to tell me it's happening in
nfs4_free_lock_state, called from __rpc_execute in a kthread. (Well,
assuming that's actually the first backtrace.)
--b.
next prev parent reply other threads:[~2012-03-21 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 19:24 krb5 failures in recent nfs-for-next J. Bruce Fields
2012-03-21 19:37 ` Bryan Schumaker
2012-03-21 19:45 ` J. Bruce Fields [this message]
2012-03-21 19:56 ` Adamson, Dros
2012-03-21 19:57 ` Myklebust, Trond
2012-03-21 20:50 ` J. Bruce Fields
2012-03-21 20:53 ` Myklebust, Trond
2012-03-21 21:11 ` 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=20120321194544.GC11222@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=bjschuma@netapp.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 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.