From: Heiko Carstens <hca@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
herbert@gondor.apana.org.au, linux-s390@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v5 0/3] Fixes and rework for aes_s390
Date: Thu, 3 Sep 2026 21:33:51 +0200 [thread overview]
Message-ID: <20260903193351.12158D16-hca@linux.ibm.com> (raw)
In-Reply-To: <20260831083735.3625-1-freude@linux.ibm.com>
On Mon, Aug 31, 2026 at 10:37:31AM +0200, Harald Freudenberger wrote:
> 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
...
> 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(-)
Applied, thanks!
prev parent reply other threads:[~2026-09-03 19:34 UTC|newest]
Thread overview: 9+ 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
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
2026-09-03 19:33 ` Heiko Carstens [this message]
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=20260903193351.12158D16-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@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