From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ingo Franzki <ifranzki@linux.ibm.com>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-s390@vger.kernel.org,
Harald Freudenberger <freude@linux.ibm.com>,
Holger Dengler <dengler@linux.ibm.com>
Subject: Re: linux-next/crypto: Problem with loading paes_s390x kernel cipher since commit "crypto: api - Fix generic algorithm self-test races"
Date: Tue, 17 Sep 2024 17:29:55 +0800 [thread overview]
Message-ID: <ZulMEyvIWNtbZJHD@gondor.apana.org.au> (raw)
In-Reply-To: <6399cdf3-3bf4-4623-8be6-cd8978d11770@linux.ibm.com>
On Tue, Sep 17, 2024 at 09:31:30AM +0200, Ingo Franzki wrote:
> Hi Herbert,
>
> we noticed a failure on linux-next in our CI that came in within the last few days.
> We do a relatively simple command to open a dm-crypt device using the s390x specific PAES kernel cipher:
>
> # cryptsetup plainOpen --key-file /sys/devices/virtual/misc/pkey/protkey/protkey_aes_128 --key-size 640 --cipher paes-cbc-plain64 /dev/loop0 enc-loop
>
> This fails when the paes_s390x kernel module has not yet been loaded with the following:
>
> device-mapper: reload ioctl on enc-loop (251:23) failed: No such file or directory
Please send me your kernel config file so that I can try to reproduce
the problem.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2024-09-17 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 7:31 linux-next/crypto: Problem with loading paes_s390x kernel cipher since commit "crypto: api - Fix generic algorithm self-test races" Ingo Franzki
2024-09-17 9:29 ` Herbert Xu [this message]
2024-09-17 9:54 ` Ingo Franzki
2024-09-18 4:01 ` [PATCH] crypto: s390/paes - Fix module aliases Herbert Xu
2024-09-18 6:50 ` Ingo Franzki
2024-09-18 8:20 ` Herbert Xu
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=ZulMEyvIWNtbZJHD@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=dengler@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=ifranzki@linux.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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