From: Klaus Kudielka <klaus.kudielka@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Boris Brezillon <bbrezillon@kernel.org>,
EBALARD Arnaud <Arnaud.Ebalard@ssi.gouv.fr>,
Romain Perier <romain.perier@gmail.com>
Subject: Re: [PATCH] crypto: marvell/cesa - Avoid empty transfer descriptor
Date: Tue, 17 Jun 2025 07:32:28 +0200 [thread overview]
Message-ID: <043472e83b086681ff3a6d0130bfa01ceeff5fa8.camel@gmail.com> (raw)
In-Reply-To: <c01e9b258e024e745ef8711bb94e0d5f6d7d4f96.camel@gmail.com>
Hello,
Plain v6.16-rc1 with marvell-cesa as module and CRYPTO_SELFTESTS enabled.
Identical behaviour as reported previously with the cryptodev tree (see below).
According to /proc/crypto, all marvell-cesa selftests (including ahash) appear to pass reliably again.
If we can trust the information in /proc/crypto, I would suggest to revert commit
e845d2399a00f866f287e0cefbd4fc7d8ef0d2f7 ("crypto: marvell/cesa - Disable hash algorithms")
Best regards, Klaus
On Fri, 2025-05-16 at 19:36 +0200, Klaus Kudielka wrote:
> On Fri, 2025-05-16 at 12:12 +0800, Herbert Xu wrote:
> >
> > Something doesn't look right. There are zero ahash lines in your
> > dmesg. IOW all the output was from skcipher tests alone.
> >
> > That could explain why ahash appears to be working.
> >
> > What does /proc/crypto show after boot-up? Do the cesa ahash
> > algorithms show up as tested in there?
> >
> > Cheers,
>
> Plain cryptodev tree, marvell-cesa as module.
> Directly after boot, only the builtin crc32c-generic shows up.
> After loading the module, the marvell-cesa ahash show up with "selftest : passed".
> But whether they REALLY were tested, I can't say.
>
> # cat /proc/crypto
> name : crc32c
> driver : crc32c-generic
> module : kernel
> priority : 100
> refcnt : 1
> selftest : passed
> internal : no
> type : shash
> blocksize : 1
> digestsize : 4
>
> # modprobe marvell-cesa
> # cat /proc/crypto
> name : hmac(sha256)
> driver : mv-hmac-sha256
> module : marvell_cesa
> priority : 0
> refcnt : 1
> selftest : passed
> internal : no
> type : ahash
> async : yes
> blocksize : 64
> digestsize : 32
>
> name : hmac(sha1)
> driver : mv-hmac-sha1
> module : marvell_cesa
> priority : 0
> refcnt : 1
> selftest : passed
> internal : no
> type : ahash
> async : yes
> blocksize : 64
> digestsize : 20
>
> name : hmac(md5)
> driver : mv-hmac-md5
> module : marvell_cesa
> priority : 0
> refcnt : 1
> selftest : passed
> internal : no
> type : ahash
> async : yes
> blocksize : 64
> digestsize : 16
>
> name : sha256
> driver : mv-sha256
> module : marvell_cesa
> priority : 0
> refcnt : 1
> selftest : passed
> internal : no
> type : ahash
> async : yes
> blocksize : 64
> digestsize : 32
>
> name : sha1
> driver : mv-sha1
> module : marvell_cesa
> priority : 0
> refcnt : 1
> selftest : passed
> internal : no
> type : ahash
> async : yes
> blocksize : 64
> digestsize : 20
>
> name : md5
> driver : mv-md5
> module : marvell_cesa
> priority : 0
> refcnt : 1
> selftest : passed
> internal : no
> type : ahash
> async : yes
> blocksize : 64
> digestsize : 16
>
> name : cbc(aes)
> driver : mv-cbc-aes
> module : marvell_cesa
> priority : 300
> refcnt : 1
> selftest : passed
> internal : no
> type : skcipher
> async : yes
> blocksize : 16
> min keysize : 16
> max keysize : 32
> ivsize : 16
> chunksize : 16
> walksize : 16
> statesize : 0
>
> name : ecb(aes)
> driver : mv-ecb-aes
> module : marvell_cesa
> priority : 300
> refcnt : 1
> selftest : passed
> internal : no
> type : skcipher
> async : yes
> blocksize : 16
> min keysize : 16
> max keysize : 32
> ivsize : 0
> chunksize : 16
> walksize : 16
> statesize : 0
>
> name : cbc(des3_ede)
> driver : mv-cbc-des3-ede
> module : marvell_cesa
> priority : 300
> refcnt : 1
> selftest : passed
> internal : no
> type : skcipher
> async : yes
> blocksize : 8
> min keysize : 24
> max keysize : 24
> ivsize : 8
> chunksize : 8
> walksize : 8
> statesize : 0
>
> name : ecb(des3_ede)
> driver : mv-ecb-des3-ede
> module : marvell_cesa
> priority : 300
> refcnt : 1
> selftest : passed
> internal : no
> type : skcipher
> async : yes
> blocksize : 8
> min keysize : 24
> max keysize : 24
> ivsize : 0
> chunksize : 8
> walksize : 8
> statesize : 0
>
> name : cbc(des)
> driver : mv-cbc-des
> module : marvell_cesa
> priority : 300
> refcnt : 1
> selftest : passed
> internal : no
> type : skcipher
> async : yes
> blocksize : 8
> min keysize : 8
> max keysize : 8
> ivsize : 8
> chunksize : 8
> walksize : 8
> statesize : 0
>
> name : ecb(des)
> driver : mv-ecb-des
> module : marvell_cesa
> priority : 300
> refcnt : 1
> selftest : passed
> internal : no
> type : skcipher
> async : yes
> blocksize : 8
> min keysize : 8
> max keysize : 8
> ivsize : 0
> chunksize : 8
> walksize : 8
> statesize : 0
>
> name : crc32c
> driver : crc32c-generic
> module : kernel
> priority : 100
> refcnt : 1
> selftest : passed
> internal : no
> type : shash
> blocksize : 1
> digestsize : 4
>
> # dmesg | tail
> [ 4.883366] mv88e6085 f1072004.mdio-mii:10 lan2: configuring for phy/gmii link mode
> [ 4.884517] br0: port 3(lan4) entered blocking state
> [ 4.884527] br0: port 3(lan4) entered forwarding state
> [ 88.867746] marvell-cesa f1090000.crypto: CESA device successfully registered
> [ 89.034292] alg: skcipher: skipping comparison tests for mv-cbc-des because cbc(des-generic) is unavailable
> [ 89.045265] alg: skcipher: skipping comparison tests for mv-cbc-des3-ede because cbc(des3_ede-generic) is unavailable
> [ 89.052456] alg: skcipher: skipping comparison tests for mv-cbc-aes because cbc(aes-generic) is unavailable
> [ 89.099763] alg: skcipher: skipping comparison tests for mv-ecb-aes because ecb(aes-generic) is unavailable
> [ 89.099819] alg: skcipher: skipping comparison tests for mv-ecb-des3-ede because ecb(des3_ede-generic) is unavailable
> [ 89.099908] alg: skcipher: skipping comparison tests for mv-ecb-des because ecb(des-generic) is unavailable
next prev parent reply other threads:[~2025-06-17 5:32 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ef7c7a96a73161e0f5061503242a8d3eddef121f.camel@gmail.com>
2024-10-06 9:11 ` [REGRESSION] alg: ahash: Several tests fail during boot on Turris Omnia Herbert Xu
2024-10-06 9:23 ` Klaus Kudielka
2024-10-07 8:27 ` Herbert Xu
2024-10-07 20:57 ` Klaus Kudielka
2024-10-09 8:34 ` Herbert Xu
2024-10-09 8:38 ` [PATCH] crypto: marvell/cesa - Disable hash algorithms Herbert Xu
2024-10-09 16:48 ` [REGRESSION] alg: ahash: Several tests fail during boot on Turris Omnia Klaus Kudielka
2024-10-10 6:05 ` Herbert Xu
2024-10-10 8:24 ` Herbert Xu
2024-10-10 17:35 ` Klaus Kudielka
2024-10-15 4:52 ` Herbert Xu
2024-10-15 17:38 ` Klaus Kudielka
2024-10-16 4:27 ` Herbert Xu
2024-10-16 5:51 ` Klaus Kudielka
2024-10-16 9:53 ` Herbert Xu
2024-11-12 19:33 ` Klaus Kudielka
2024-11-13 9:57 ` Thorsten Leemhuis
2025-05-06 13:19 ` Herbert Xu
2025-05-07 8:43 ` [PATCH] crypto: marvell/cesa - Do not chain submitted requests Herbert Xu
2025-05-07 15:16 ` Corentin Labbe
2025-05-08 5:15 ` [v2 PATCH] " Herbert Xu
2025-05-08 5:22 ` [v3 " Herbert Xu
2025-05-08 12:53 ` Corentin Labbe
2025-05-08 13:10 ` Herbert Xu
2025-05-08 13:43 ` Corentin Labbe
2025-05-09 3:13 ` Herbert Xu
2025-05-09 3:19 ` Herbert Xu
2025-05-09 8:11 ` Herbert Xu
2025-05-09 11:01 ` Corentin Labbe
2025-05-10 1:15 ` Herbert Xu
2025-05-10 1:37 ` Herbert Xu
2025-05-10 1:44 ` Herbert Xu
2025-05-10 10:41 ` [PATCH] crypto: marvell/cesa - Handle zero-length skcipher requests Herbert Xu
2025-05-10 8:32 ` [v3 PATCH] crypto: marvell/cesa - Do not chain submitted requests Klaus Kudielka
2025-05-10 9:05 ` Herbert Xu
2025-05-10 9:38 ` Klaus Kudielka
2025-05-10 10:19 ` Herbert Xu
2025-05-10 10:43 ` [PATCH] crypto: marvell/cesa - Avoid empty transfer descriptor Herbert Xu
2025-05-10 11:14 ` Corentin Labbe
2025-05-10 11:39 ` Herbert Xu
2025-05-10 13:02 ` Herbert Xu
2025-05-10 15:07 ` Klaus Kudielka
2025-05-11 3:22 ` Herbert Xu
2025-05-11 16:39 ` Klaus Kudielka
2025-05-13 9:20 ` Herbert Xu
2025-05-14 5:12 ` Klaus Kudielka
2025-05-14 5:14 ` Herbert Xu
2025-05-15 17:53 ` Klaus Kudielka
2025-05-15 18:21 ` Eric Biggers
2025-05-15 18:45 ` Klaus Kudielka
2025-05-15 23:25 ` Herbert Xu
2025-05-16 12:41 ` Corentin Labbe
2025-05-16 12:45 ` Herbert Xu
2025-05-17 11:24 ` Corentin Labbe
2025-05-18 7:58 ` Herbert Xu
2025-05-21 5:06 ` Herbert Xu
2025-05-21 9:16 ` Herbert Xu
2025-05-21 9:58 ` Arnd Bergmann
2025-05-21 10:24 ` Herbert Xu
2025-05-21 11:36 ` Arnd Bergmann
2025-05-22 3:13 ` Herbert Xu
2025-05-22 20:08 ` Corentin Labbe
2025-05-21 10:45 ` Corentin Labbe
2025-05-21 10:56 ` Herbert Xu
2025-05-21 13:58 ` Corentin Labbe
2025-05-22 3:01 ` crypto: marvell/cesa - dma_alloc_coherent broken but kmalloc + dma_map_single works Herbert Xu
2025-05-22 7:38 ` Herbert Xu
2025-05-22 20:07 ` Corentin Labbe
2025-05-23 11:46 ` Herbert Xu
2025-05-28 9:58 ` Herbert Xu
2025-05-29 11:17 ` Corentin Labbe
2025-05-22 11:13 ` Herbert Xu
2025-05-16 4:12 ` [PATCH] crypto: marvell/cesa - Avoid empty transfer descriptor Herbert Xu
2025-05-16 17:36 ` Klaus Kudielka
2025-06-17 5:32 ` Klaus Kudielka [this message]
2025-06-17 5:36 ` Herbert Xu
2025-05-08 12:49 ` [v2 PATCH] crypto: marvell/cesa - Do not chain submitted requests Corentin Labbe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=043472e83b086681ff3a6d0130bfa01ceeff5fa8.camel@gmail.com \
--to=klaus.kudielka@gmail.com \
--cc=Arnaud.Ebalard@ssi.gouv.fr \
--cc=bbrezillon@kernel.org \
--cc=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=romain.perier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox