From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/2] crypto: fix handling & reporting of errors when erasing keyslots
Date: Fri, 23 Oct 2026 15:13:01 +0100 [thread overview]
Message-ID: <20261023141303.163893-1-berrange@redhat.com> (raw)
Daniel P. Berrangé (2):
crypto: avoid overwriting Error object erasing keyslot
crypto: add newline in error hint messages
crypto/block-luks.c | 25 +++++++++++++++++--------
1 file changed, 17 insertions(+), 8 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-23 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 14:13 Daniel P. Berrangé [this message]
2026-10-23 14:13 ` [PATCH 1/2] crypto: avoid overwriting Error object erasing keyslot Daniel P. Berrangé
2026-10-23 20:08 ` marcandre.lureau
2026-10-26 5:20 ` Markus Armbruster
2026-10-23 14:13 ` [PATCH 2/2] crypto: add newline in error hint messages Daniel P. Berrangé
2026-10-23 20:08 ` marcandre.lureau
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=20261023141303.163893-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.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.