From: "Tuomas Räsänen" <tuomasjjrasanen@opinsys.fi>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Veli-Matti Lintu <veli-matti.lintu@opinsys.fi>,
linux-nfs@vger.kernel.org
Subject: Re: Kernels 3.7 and newer break rpc.gssd -n
Date: Fri, 15 Feb 2013 12:00:31 +0000 (UTC) [thread overview]
Message-ID: <654867786.10283.1360929631448.JavaMail.root@opinsys.fi> (raw)
In-Reply-To: <CED6E6AF-B551-4099-89CE-861E5F46D31A@oracle.com>
----- Original Message -----
> From: "Chuck Lever" <chuck.lever@oracle.com>
>
> Have you tried a kernel at commit 05f4c350 but with the compilation fix
> applied, then one with 05f4c350 removed, to confirm that this indeed is the
> commit that introduces the problem?
Yes. With commit 05f4c350 + the compilation fix, the problem occurs, but without
05f4c350, the parent (6f2ea7f) works as expected, requesting for service <null>.
>
> When the mount operation fails, is it the first time this client attempts to
> mount a share on server.example.org, or does the client already have mounts
> of server.example.org, possibly using other security flavors?
Yes, the problem occurs on the very first mount attempt.
--
Tuomas
next prev parent reply other threads:[~2013-02-15 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <471074187.98491.1360768929786.JavaMail.root@opinsys.fi>
2013-02-13 15:29 ` Kernels 3.7 and newer break rpc.gssd -n Veli-Matti Lintu
2013-02-14 14:24 ` Veli-Matti Lintu
2013-02-14 15:39 ` Chuck Lever
2013-02-15 12:00 ` Tuomas Räsänen [this message]
2013-02-15 16:33 ` Chuck Lever
2013-02-18 8:23 ` Veli-Matti Lintu
2013-02-18 15:26 ` Chuck Lever
2013-02-14 15:57 ` Chuck Lever
2013-02-18 21:16 ` Chuck Lever
2013-02-18 22:48 ` Chuck Lever
2013-02-18 23:14 ` Myklebust, Trond
2013-02-19 0:10 ` Chuck Lever
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=654867786.10283.1360929631448.JavaMail.root@opinsys.fi \
--to=tuomasjjrasanen@opinsys.fi \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=veli-matti.lintu@opinsys.fi \
/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