[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aC-EGr50MIVJqwVn@Red>
Date: Thu, 22 May 2025 22:07:54 +0200
From: Corentin Labbe <clabbe.montjoie@...il.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Klaus Kudielka <klaus.kudielka@...il.com>,
Eric Biggers <ebiggers@...nel.org>, regressions@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Boris Brezillon <bbrezillon@...nel.org>,
EBALARD Arnaud <Arnaud.Ebalard@....gouv.fr>,
Romain Perier <romain.perier@...il.com>,
Arnd Bergmann <arnd@...db.de>, Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Gregory Clement <gregory.clement@...tlin.com>,
Christoph Hellwig <hch@...radead.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Subject: Re: crypto: marvell/cesa - dma_alloc_coherent broken but kmalloc +
dma_map_single works
Le Thu, May 22, 2025 at 03:38:20PM +0800, Herbert Xu a écrit :
> On Thu, May 22, 2025 at 11:01:36AM +0800, Herbert Xu wrote:
> >
> > So here is the latest debugging patch with dma_map_single on top
> > of cryptodev. Note that the partial hash mismatch code is buggy
> > but it doesn't matter because it still prints enough info for us
> > to interpret.
>
> Oops, I screwed up that patch. Here is the corrected version.
>
Hello
Here is the result:
http://kernel.montjoie.ovh/479404.log
I have built by adding also your "crypto: marvell/cesa - Fix engine load inaccuracy"
Thanks
Regards
Powered by blists - more mailing lists