public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Veli-Matti Lintu <veli-matti.lintu@opinsys.fi>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Tuomas Räsänen" <tuomasjjrasanen@opinsys.fi>, linux-nfs@vger.kernel.org
Subject: Re: Kernels 3.7 and newer break rpc.gssd -n
Date: Mon, 18 Feb 2013 08:23:12 +0000 (UTC)	[thread overview]
Message-ID: <505003638.18320.1361175792539.JavaMail.root@opinsys.fi> (raw)
In-Reply-To: <74874B5C-CDDE-4F77-B69D-FC40FF5DD933@oracle.com>

> > 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.
> 
> Thanks for confirming.  Did you try updating nfs-utils on your NFS client to
> 1.2.8-rc1 or later (specifically to replace rpc.gssd)?

Yes, gssd from nfs-utils 1.2.8-rc3 behaves the same way and fails when service 
name is not null.

The code in gssd that checks for the service name seems to be the same if I
understand the code correctly.

http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=blob;f=utils/gssd/gssd_proc.c;h=c17ab3bf914526f433fb6c76ace1daa63c10d921;hb=HEAD#l985

---------------------------------------------------------------------------------
        if (uid != 0 || (uid == 0 && root_uses_machine_creds == 0 &&
                                service == NULL)) {
                /* Tell krb5 gss which credentials cache to use */
                for (dirname = ccachesearch; *dirname != NULL; dirname++) {
                        err = gssd_setup_krb5_user_gss_ccache(uid, clp->servername, *dirname);
                        if (err == -EKEYEXPIRED)
                                downcall_err = -EKEYEXPIRED;
                        else if (!err)
                                create_resp = create_auth_rpc_client(clp, &rpc_clnt, &auth, uid,
                                                             AUTHTYPE_KRB5);
                        if (create_resp == 0)
                                break;
                }
        }
---------------------------------------------------------------------------------

Veli-Matti

  reply	other threads:[~2013-02-18  8:27 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
2013-02-15 16:33         ` Chuck Lever
2013-02-18  8:23           ` Veli-Matti Lintu [this message]
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=505003638.18320.1361175792539.JavaMail.root@opinsys.fi \
    --to=veli-matti.lintu@opinsys.fi \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tuomasjjrasanen@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