From: "J. Bruce Fields" <bfields@fieldses.org>
To: Bryan Schumaker <bjschuma@netapp.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: krb5 failures in recent nfs-for-next
Date: Wed, 21 Mar 2012 15:24:49 -0400 [thread overview]
Message-ID: <20120321192448.GB11222@fieldses.org> (raw)
Have you been doing any krb5 testing?
I'm seeing the client crash as of nfs-for-next, and haven't been able to
get any debugging out of it so far.
--b.
next reply other threads:[~2012-03-21 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 19:24 J. Bruce Fields [this message]
2012-03-21 19:37 ` krb5 failures in recent nfs-for-next Bryan Schumaker
2012-03-21 19:45 ` J. Bruce Fields
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=20120321192448.GB11222@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox