[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aC-EPvRG8oBND0wA@Red>
Date: Thu, 22 May 2025 22:08:30 +0200
From: Corentin Labbe <clabbe.montjoie@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
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>,
"'bbrezillon@...nel.org'" <bbrezillon@...nel.org>,
EBALARD Arnaud <Arnaud.Ebalard@....gouv.fr>,
Romain Perier <romain.perier@...il.com>
Subject: Re: [PATCH] crypto: marvell/cesa - Avoid empty transfer descriptor
Le Wed, May 21, 2025 at 01:36:06PM +0200, Arnd Bergmann a écrit :
> On Wed, May 21, 2025, at 12:24, Herbert Xu wrote:
> > On Wed, May 21, 2025 at 11:58:49AM +0200, Arnd Bergmann wrote:
> >>
> >> I did not see the entire background of the discussion, but would
> >> point out that this is not supposed to work at all:
> >
> > We're trying to find out why this driver fails under concurrent
> > load. It works perfectly if you do one request at a time, but
> > when you hit it with load coming from both CPUs, it ends up
> > corrupting the data.
>
> Ok. Which SoC exactly is this on? Armada XP or Armada 385?
>
It is armada-388-clearfog-pro
Powered by blists - more mailing lists