From: Michael Young <m.a.young@durham.ac.uk>
To: Eric Biggers <ebiggers@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: NFS mounts failing when keytab present on client
Date: Tue, 27 Mar 2018 23:06:14 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.1803272126070.3013@austen3.home> (raw)
NFS mounts stopped working on one of my computers after a kernel update
from 4.15.3 to 4.15.4. I traced the problem to the commit
[46e8d06e423c4f35eac7a8b677b713b3ec9b0684] crypto: hash - prevent using
keyed hashes without setting key
and a later kernel with this patch reverted works normally.
The problem seems to be related to kerberos as the mount fails when the
keytab is present, but works if I rename the keytab file. This is true
even though the mount is with sec=sys . The mount should also work with
sec=krb5 but that also fails in the same way. When the mount fails there
are errors in dmesg like
[ 1232.522816] gss_marshal: gss_get_mic FAILED (851968)
[ 1232.522819] RPC: couldn't encode RPC header, exit EIO
[ 1232.522856] gss_marshal: gss_get_mic FAILED (851968)
[ 1232.522857] RPC: couldn't encode RPC header, exit EIO
[ 1232.522863] NFS: nfs4_discover_server_trunking unhandled error -5.
Exiting with error EIO
[ 1232.525039] gss_marshal: gss_get_mic FAILED (851968)
[ 1232.525042] RPC: couldn't encode RPC header, exit EIO
Michael Young
next reply other threads:[~2018-03-27 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 22:06 Michael Young [this message]
2018-03-27 22:29 ` NFS mounts failing when keytab present on client Eric Biggers
2018-03-28 8:00 ` M A Young
2018-03-28 17:47 ` Eric Biggers
2018-03-28 15:46 ` J. Bruce Fields
2018-03-28 17:50 ` Eric Biggers
2018-03-28 18:03 ` J. Bruce Fields
2018-03-28 18:04 ` 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=alpine.LFD.2.21.1803272126070.3013@austen3.home \
--to=m.a.young@durham.ac.uk \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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).