From: Sami Tolvanen <samitolvanen@google.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Akilesh Kailash <akailash@google.com>,
kernel-team@android.com, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Milan Broz <gmazyland@gmail.com>,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dm-verity: do forward error correction on metadata I/O errors
Date: Wed, 19 Feb 2025 23:47:34 +0000 [thread overview]
Message-ID: <20250219234734.GA758416@google.com> (raw)
In-Reply-To: <920de20f-1d11-e6f6-e7ae-a774f5c210f0@redhat.com>
On Mon, Feb 17, 2025 at 10:36:02PM +0100, Mikulas Patocka wrote:
> dm-verity: do forward error correction on metadata I/O errors
>
> Do forward error correction if metadata I/O fails.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>
> ---
> drivers/md/dm-verity-target.c | 25 +++++++++++++++++++++----
> 1 file changed, 21 insertions(+), 4 deletions(-)
>
> Index: linux-2.6/drivers/md/dm-verity-target.c
> ===================================================================
> --- linux-2.6.orig/drivers/md/dm-verity-target.c 2025-02-10 16:24:56.000000000 +0100
> +++ linux-2.6/drivers/md/dm-verity-target.c 2025-02-17 16:47:37.000000000 +0100
> @@ -311,7 +311,7 @@ static int verity_verify_level(struct dm
>
> if (static_branch_unlikely(&use_bh_wq_enabled) && io->in_bh) {
> data = dm_bufio_get(v->bufio, hash_block, &buf);
> - if (data == NULL) {
> + if (IS_ERR_OR_NULL(data)) {
Thanks for adding the check, makes this easier to follow.
> /*
> * In tasklet and the hash was not in the bufio cache.
> * Return early and resume execution from a work-queue
> @@ -324,8 +324,24 @@ static int verity_verify_level(struct dm
> &buf, bio->bi_ioprio);
> }
>
> - if (IS_ERR(data))
> - return PTR_ERR(data);
> + if (IS_ERR(data)) {
> + if (skip_unverified)
> + return 1;
> + r = PTR_ERR(data);
> + data = dm_bufio_new(v->bufio, hash_block, &buf);
> + if (IS_ERR(data))
> + return r;
> + if (verity_fec_decode(v, io, DM_VERITY_BLOCK_TYPE_METADATA,
> + hash_block, data) == 0) {
> + aux = dm_bufio_get_aux_data(buf);
> + aux->hash_verified = 1;
> + goto release_ok;
> + } else {
> + dm_bufio_release(buf);
> + dm_bufio_forget(v->bufio, hash_block);
> + return r;
> + }
> + }
>
> aux = dm_bufio_get_aux_data(buf);
>
> @@ -366,6 +382,7 @@ static int verity_verify_level(struct dm
> }
> }
>
> +release_ok:
> data += offset;
> memcpy(want_digest, data, v->digest_size);
> r = 0;
> @@ -1761,7 +1778,7 @@ static struct target_type verity_target
> .name = "verity",
> /* Note: the LSMs depend on the singleton and immutable features */
> .features = DM_TARGET_SINGLETON | DM_TARGET_IMMUTABLE,
> - .version = {1, 10, 0},
> + .version = {1, 11, 0},
> .module = THIS_MODULE,
> .ctr = verity_ctr,
> .dtr = verity_dtr,
Reviewed-by: Sami Tolvanen <samitolvanen@google.com>
Sami
next prev parent reply other threads:[~2025-02-19 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 21:36 [PATCH v2] dm-verity: do forward error correction on metadata I/O errors Mikulas Patocka
2025-02-19 23:47 ` Sami Tolvanen [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-10 15:04 [PATCH] " Mikulas Patocka
2025-02-10 16:39 ` Milan Broz
2025-02-10 16:46 ` [PATCH v2] " Mikulas Patocka
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=20250219234734.GA758416@google.com \
--to=samitolvanen@google.com \
--cc=agk@redhat.com \
--cc=akailash@google.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=gmazyland@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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