linux-kernel - Re: Intel QAT on A2SDi-8C-HLN4F causes massive data corruption with dm-crypt + xfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 2 Mar 2022 11:29:00 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Herbert Xu <herbert@...dor.apana.org.au>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Giovanni Cabiddu <giovanni.cabiddu@...el.com>,
        Kyle Sanderson <kyle.leet@...il.com>,
        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>
Subject: Re: Intel QAT on A2SDi-8C-HLN4F causes massive data corruption with
 dm-crypt + xfs

On Tue, Mar 01, 2022 at 04:11:13PM +1200, Herbert Xu wrote:
> On Mon, Feb 28, 2022 at 05:12:20PM -0800, Linus Torvalds wrote:
> > 
> > It sounds like it was incidental and almost accidental that it fixed
> > that thing, and nobody realized it should perhaps be also moved to
> > stable.
> 
> Yes this was incidental.  The patch in question fixes an issue in
> OOM situations where drivers that must allocate memory on each
> request may lead to dead-lock so it's not really targeted at qat.

Ok, so what commits should I backport to kernels older than 5.10 to
resolve this?

thanks,

greg k-h