From: Harald Freudenberger <freude@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
herbert@gondor.apana.org.au
Cc: freude@linux.ibm.com, linux-s390@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: [PATCH v5 0/3] Fixes and rework for aes_s390
Date: Mon, 31 Aug 2026 10:37:32 +0200 [thread overview]
Message-ID: <20260831083735.3625-2-freude@linux.ibm.com> (raw)
In-Reply-To: <20260831083735.3625-1-freude@linux.ibm.com>
Fix and rework some issues around arch/s390/aes_s390.c:
- Fix skcipher_walk return code handling in aes_s390
- Add scrub of some temp buffers
- Shift from using a mutex to using a semaphore in AES CTR
For more details please see patch headers.
Changelog:
v1: initial version
v2: Fix missing scrub on a temp buffer used to process left over bytes
in CTR mode.
v3: - Yet another buffer scrubbing was missing. Added to the 2nd
patch and rephrased commit header.
- Added patch to fix one warning with context analysis regarding
the handling of a mutex with the AES CTR implementation.
v4: - Sashiko found yet another buffer which was not scrubbed.
- New patch #3 which shifts from using a mutex to using a
semaphore in AES CTR as this algorithm may be invoked in
atomic/interrupt context.
- With the shift to a semaphore now clang is able to do the
context analysis. So the patch from v3 which reworked the CTR
implementation is not needed any more. Note that paes still has
the issue with clang context analysis, but this will be
addressed in another patch series.
v5: - Added R-Bs
- Reworked the mutex to semaphore patch to also cover the need to
get rid of the conditional locking.
Harald Freudenberger (3):
s390/crypto: Fix skcipher_walk return code handling in aes_s390
s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm
algorithm
s390/crypto: Fix use of mutex in atomic context
arch/s390/crypto/aes_s390.c | 87 +++++++++++++++++++++++--------------
1 file changed, 55 insertions(+), 32 deletions(-)
base-commit: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f
--
2.43.0
next prev parent reply other threads:[~2026-08-31 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 8:37 [PATCH v5 0/3] Fixes and rework for aes_s390 Harald Freudenberger
2026-08-31 8:37 ` Harald Freudenberger [this message]
2026-08-31 8:37 ` [PATCH v5 1/3] s390/crypto: Fix skcipher_walk return code handling in aes_s390 Harald Freudenberger
2026-08-31 8:49 ` sashiko-bot
2026-08-31 8:37 ` [PATCH v5 2/3] s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm Harald Freudenberger
2026-08-31 9:05 ` sashiko-bot
2026-08-31 8:37 ` [PATCH v5 3/3] s390/crypto: Fix use of mutex in atomic context Harald Freudenberger
2026-08-31 9:10 ` sashiko-bot
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=20260831083735.3625-2-freude@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--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