From: Pierre Sauter <pierre.sauter@stwm.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
matthew.ruffell@canonical.com,
linux-stable <stable@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-kernel-owner@vger.kernel.org
Subject: Re: [Regression] "SUNRPC: Add "@len" parameter to gss_unwrap()" breaks NFS Kerberos on upstream stable 5.4.y
Date: Fri, 17 Jul 2020 19:29:44 +0200 [thread overview]
Message-ID: <4546230.GXAFRqVoOG@keks.as.studentenwerk.mhn.de> (raw)
In-Reply-To: <0885F62B-F9D2-4248-9313-70DAA1A1DE71@oracle.com>
Hi Chuck,
Am Donnerstag, 16. Juli 2020, 21:25:40 CEST schrieb Chuck Lever:
> So this makes me think there's a possibility you are not using upstream
> stable kernels. I can't help if I don't know what source code and commit
> stream you are using. It also makes me question the bisect result.
Yes you are right, I was referring to Ubuntu kernels 5.4.0-XX. From the
discussion in the Ubuntu bugtracker I got the impression that Ubuntu kernels
5.4.0-XX and upstream 5.4.XX are closely related, obviously they are not. The
bisection was done by the original bug reporter and also refers to the Ubuntu
kernel.
In the meantime I tested v5.4.51 upstream, which shows no problems. Sorry for
the bother.
> > My krb5 etype is aes256-cts-hmac-sha1-96.
>
> Thanks! And what is your NFS server and filesystem? It's possible that the
> client is not estimating the size of the reply correctly. Variables include
> the size of file handles, MIC verifiers, and wrap tokens.
The server is Debian with v4.19.130 upstream, filesystem ext4.
> You might try:
>
> e8d70b321ecc ("SUNRPC: Fix another issue with MIC buffer space")
That one is actually in Ubuntus 5.4.0-40, from looking at the code.
Best Regards
--
Pierre Sauter
Studentenwerk München
-------
next prev parent reply other threads:[~2020-07-17 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 14:48 [Regression] "SUNRPC: Add "@len" parameter to gss_unwrap()" breaks NFS Kerberos on upstream stable 5.4.y Kai-Heng Feng
2020-07-15 15:02 ` Chuck Lever
2020-07-15 15:08 ` Kai-Heng Feng
2020-07-15 15:14 ` Chuck Lever
2020-07-15 18:54 ` Chuck Lever
2020-07-16 18:40 ` Pierre Sauter
2020-07-16 19:25 ` Chuck Lever
2020-07-17 17:29 ` Pierre Sauter [this message]
2020-07-17 17:34 ` Chuck Lever
2020-07-17 17:56 ` Kai-Heng Feng
2020-07-17 19:46 ` Pierre Sauter
2020-07-18 15:55 ` Chuck Lever
2020-07-20 21:22 ` 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=4546230.GXAFRqVoOG@keks.as.studentenwerk.mhn.de \
--to=pierre.sauter@stwm.de \
--cc=chuck.lever@oracle.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=matthew.ruffell@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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).