Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4;
MIME-Version: 1.0
References: <CACsaVZ+LkHwTKO4XE_FFM62SbF3gGD4DZyse-9Y1UbJUgrhvfA@mail.gmail.com>
 <ZQPxuZ2tifa9bQKJ@gcabiddu-mobl1.ger.corp.intel.com>
In-Reply-To: <ZQPxuZ2tifa9bQKJ@gcabiddu-mobl1.ger.corp.intel.com>
From:   Kyle Sanderson <kyle.leet@gmail.com>
Date:   Wed, 4 Oct 2023 20:55:34 -0700
Message-ID: <CACsaVZJYcGv26gM=Kcm2R3-A7Yqc9Jc1cd8TchA0POpxx1NHow@mail.gmail.com>
Subject: Re: Linux 6.1.52 regression: Intel QAT kernel panic (memory corruption)
To:     Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Cc:     Linux-Kernal <linux-kernel@vger.kernel.org>, qat-linux@intel.com,
        Greg KH <gregkh@linuxfoundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Thu, Sep 14, 2023 at 10:55=E2=80=AFPM Giovanni Cabiddu
<giovanni.cabiddu@intel.com> wrote:
>
> On Thu, Sep 14, 2023 at 10:27:22PM -0700, Kyle Sanderson wrote:
> > Hello Intel QAT Maintainers,
> >
> > It looks like QAT has regressed again. The present symptom is just
> > straight up memory corruption. I was running Canonical 6.1.0-1017-oem
> > and it doesn't happen, with 6.1.0-1020-oem and 6.1.0-1021-oem it does.
> > I don't know what these map to upstream, however with NixOS installed
> > the same corruption failure occurs on 6.1.52.
> This is probably be related to [1].
> Versions from 6.1.39 to 6.1.52 are affected. Fixed in v6.1.53.
>
> [1] https://www.spinics.net/lists/stable/msg678947.html
>
> Regards,
>
> --
> Giovanni

Thank you Giovanni - that appears to have been it. Ubuntu
6.1.0-1023-oem (v6.1.53) no longer reproduces the issue.

K.

On Thu, Sep 14, 2023 at 10:55=E2=80=AFPM Giovanni Cabiddu
<giovanni.cabiddu@intel.com> wrote:
>
> On Thu, Sep 14, 2023 at 10:27:22PM -0700, Kyle Sanderson wrote:
> > Hello Intel QAT Maintainers,
> >
> > It looks like QAT has regressed again. The present symptom is just
> > straight up memory corruption. I was running Canonical 6.1.0-1017-oem
> > and it doesn't happen, with 6.1.0-1020-oem and 6.1.0-1021-oem it does.
> > I don't know what these map to upstream, however with NixOS installed
> > the same corruption failure occurs on 6.1.52. The stack traces give
> > illegal instructions and all kinds of badness across all modules when
> > the device is simply present on the system, resulting in a hung
> > system, or a multitude of processes crashing and the system failing to
> > start. Disabling the device in the system BIOS results in a working
> > system, and no extreme corruption. kmem_cache_alloc_node is the common
> > fixture in the traces (I don't have a serial line), but I suspect
> > that's not where the problem is. The corruption this time happens
> > without block crypto being involved, and simply booting the installer
> > from a USB stick.
> This is probably be related to [1].
> Versions from 6.1.39 to 6.1.52 are affected. Fixed in v6.1.53.
>
> [1] https://www.spinics.net/lists/stable/msg678947.html
>
> Regards,
>
> --
> Giovanni