[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yh0y75aegqS4jIP7@silpixa00400314>
Date: Mon, 28 Feb 2022 20:39:11 +0000
From: Giovanni Cabiddu <giovanni.cabiddu@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Kyle Sanderson <kyle.leet@...il.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Dave Chinner <david@...morbit.com>, qat-linux@...el.com,
Linux-Kernal <linux-kernel@...r.kernel.org>,
linux-xfs <linux-xfs@...r.kernel.org>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
device-mapper development <dm-devel@...hat.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: Intel QAT on A2SDi-8C-HLN4F causes massive data corruption with
dm-crypt + xfs
On Mon, Feb 28, 2022 at 11:25:49AM -0800, Linus Torvalds wrote:
> On Mon, Feb 28, 2022 at 12:18 AM Kyle Sanderson <kyle.leet@...il.com> wrote:
> >
> > Makes sense - this kernel driver has been destroying users for many
> > years. I'm disappointed that this critical bricking failure isn't
> > searchable for others.
>
> It does sound like we should just disable that driver entirely until
> it is fixed.
>
> Or at least the configuration that can cause problems, if there is
> some particular sub-case.
The dm-crypt + QAT use-case is already disabled since kernel 5.10 due to
a different issue.
Is it an option to port those patches to stable till I provide a fix for
the driver? I drafted already few alternatives for the fix and I am aiming
for a final set by end of week.
Thanks,
--
Giovanni
Powered by blists - more mailing lists