From: "Brian J. Murrell" <brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Re: different kernels mean NFS4/GSSAPI works or doesn't
Date: Wed, 23 Mar 2011 11:07:11 -0400 [thread overview]
Message-ID: <4D8A0C9F.8090300@interlinx.bc.ca> (raw)
In-Reply-To: <AANLkTi=b1z0MrYYQmidbra0EHanegcLO5qoOScLq21rb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On 11-03-23 10:29 AM, Kevin Coffman wrote:
>
> However, that doesn't appear to be the case from looking at the
> gssd/svcgssd output. Have you checked the server's syslog for
> messages about rpc.gssd not running?
Yup. Nothing there.
> OK. Thanks. There is enough info there, even with the redaction.
Ahhh. Good.
> This shows that a des (enctype 4) session key is being negotiated and
> delivered to both kernels, so I don't think any of the Kerberos issues
> should be involved here. (At least from the user-land perspective.)
Hrm. So this gets even more interesting (for some values of "interesting").
> I'm not sure what kernel change would be causing your hang ...
Thanks for looking though.
I'm open to any more ideas, debugging info requests, etc. that anyone
might have.
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-03-23 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 23:27 different kernels mean NFS4/GSSAPI works or doesn't Brian J. Murrell
2011-03-23 2:41 ` Kevin Coffman
2011-03-23 11:03 ` Brian J. Murrell
2011-03-23 14:29 ` Kevin Coffman
[not found] ` <AANLkTi=b1z0MrYYQmidbra0EHanegcLO5qoOScLq21rb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-23 15:07 ` Brian J. Murrell [this message]
2011-03-23 17:07 ` Trond Myklebust
2011-03-27 0:07 ` Brian J. Murrell
[not found] ` <1300900035.11677.12.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2011-03-27 12:42 ` Brian J. Murrell
2011-03-30 12:09 ` Brian J. Murrell
2011-04-01 13:02 ` Brian J. Murrell
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=4D8A0C9F.8090300@interlinx.bc.ca \
--to=brian-squohqy54cvwr29bmmi2ca@public.gmane.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;
as well as URLs for NNTP newsgroup(s).