From: "Adamson, Dros" <Weston.Adamson@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"<linux-nfs@vger.kernel.org>" <linux-nfs@vger.kernel.org>
Subject: Re: krb5 failures in recent nfs-for-next
Date: Wed, 21 Mar 2012 19:56:24 +0000 [thread overview]
Message-ID: <72DB89A4-DDDB-41FD-9B47-3CBECA0E5966@netapp.com> (raw)
In-Reply-To: <20120321194544.GC11222@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
Hey Bruce,
Any more info on this? nfs-for-next wfm with kerberos against a server with fedora 16 kernel 3.2.10-3.fc16.x86_64.
-dros
On Mar 21, 2012, at 3:45 PM, J. Bruce Fields wrote:
> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1374 bytes --]
next prev parent reply other threads:[~2012-03-21 19:56 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
2012-03-21 19:56 ` Adamson, Dros [this message]
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=72DB89A4-DDDB-41FD-9B47-3CBECA0E5966@netapp.com \
--to=weston.adamson@netapp.com \
--cc=Bryan.Schumaker@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--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