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>
Cc: freude@linux.ibm.com, linux-s390@vger.kernel.org
Subject: [PATCH v3 0/2] Fixes related to domain access and verification
Date: Thu, 23 Jul 2026 11:54:51 +0200 [thread overview]
Message-ID: <20260723095453.127322-1-freude@linux.ibm.com> (raw)
This is now a combination of the two patch series
"Fix wrong domain value verification with EP11 cards" and
"Close speculative mem read possibility" as there is some
code dependency between the patches.
Changelog for "Fix wrong domain value verification with EP11 cards"
v1: initial version
v2: Resend without any code changes, just Finn's reviewed by added.
Changelog for "Close speculative mem read possibility"
v1: initial version
v2: Resend without any code changes, just Finn's reviewed by added.
Changelog for v3 and further:
v3: Resent without any changes, just this time as a 2-patches series.
Harald Freudenberger (2):
s390/zcrypt: Fix wrong domain value verification with EP11 CPRBs
s390/zcrypt: Close speculative mem read possibility
drivers/s390/crypto/zcrypt_api.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2026-07-23 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 9:54 Harald Freudenberger [this message]
2026-07-23 9:54 ` [PATCH v3 1/2] s390/zcrypt: Fix wrong domain value verification with EP11 CPRBs Harald Freudenberger
2026-07-23 10:15 ` sashiko-bot
2026-07-23 9:54 ` [PATCH v3 2/2] s390/zcrypt: Close speculative mem read possibility Harald Freudenberger
2026-07-23 10:34 ` 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=20260723095453.127322-1-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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.