From: Patrick Steinhardt <ps@pks.im>
To: grub-devel@gnu.org
Cc: Daniel Kiper <dkiper@net-space.pl>
Subject: [PATCH v2 0/2] Improve LUKS2 error reporting
Date: Thu, 16 Apr 2020 19:15:06 +0200 [thread overview]
Message-ID: <cover.1587057064.git.ps@pks.im> (raw)
In-Reply-To: <af9432230fb85ee7c3b12b6115f860eaa1b16485.1587032245.git.ps@pks.im>
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
Hi,
this is the second version of my patch that has the aim of improving
error reporting for LUKS2 in case decryption of the disk fails. There's
no functional changes, but I've split up the single patch into two as
proposed by Daniel.
@Daniel: Note that I've added your Reviewed-by to the second patch, but
not to the first one as it's message is completely new.
Patrick
Patrick Steinhardt (2):
luks2: Propagate error when reading area key fails
luks2: Improve error reporting when recovering keys
grub-core/disk/luks2.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
--
2.26.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-16 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 10:19 [PATCH] luks2: Improve error reporting when decrypting/verifying key Patrick Steinhardt
2020-04-16 12:27 ` Daniel Kiper
2020-04-16 12:36 ` Patrick Steinhardt
2020-04-16 12:57 ` Daniel Kiper
2020-04-16 17:15 ` Patrick Steinhardt [this message]
2020-04-16 17:15 ` [PATCH v2 1/2] luks2: Propagate error when reading area key fails Patrick Steinhardt
2020-04-16 17:15 ` [PATCH v2 2/2] luks2: Improve error reporting when recovering keys Patrick Steinhardt
2020-04-17 13:54 ` [PATCH v2 0/2] Improve LUKS2 error reporting Daniel Kiper
2020-05-30 10:16 ` Patrick Steinhardt
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=cover.1587057064.git.ps@pks.im \
--to=ps@pks.im \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.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.