linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: chuck.lever@oracle.com
Cc: matthew.ruffell@canonical.com,
	linux-stable <stable@vger.kernel.org>,
	linux-nfs@vger.kernel.org,
	"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: [Regression] "SUNRPC: Add "@len" parameter to gss_unwrap()" breaks NFS Kerberos on upstream stable 5.4.y
Date: Wed, 15 Jul 2020 22:48:06 +0800	[thread overview]
Message-ID: <309E203B-8818-4E33-87F0-017E127788E2@canonical.com> (raw)

Hi,

Multiple users reported NFS causes NULL pointer dereference [1] on Ubuntu, due to commit "SUNRPC: Add "@len" parameter to gss_unwrap()" and commit "SUNRPC: Fix GSS privacy computation of auth->au_ralign".

The same issue happens on upstream stable 5.4.y branch.
The mainline kernel doesn't have this issue though.

Should we revert them? Or is there any missing commits need to be backported to v5.4?

[1] https://bugs.launchpad.net/bugs/1886277

Kai-Heng

             reply	other threads:[~2020-07-15 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 14:48 Kai-Heng Feng [this message]
2020-07-15 15:02 ` [Regression] "SUNRPC: Add "@len" parameter to gss_unwrap()" breaks NFS Kerberos on upstream stable 5.4.y 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
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=309E203B-8818-4E33-87F0-017E127788E2@canonical.com \
    --to=kai.heng.feng@canonical.com \
    --cc=chuck.lever@oracle.com \
    --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).