diff options
| author | Eric Biggers <ebiggers@kernel.org> | 2026-03-21 00:15:08 +0300 |
|---|---|---|
| committer | Mikulas Patocka <mpatocka@redhat.com> | 2026-03-23 19:50:52 +0300 |
| commit | 0e4c1eb59909ddaef19cd997e646d5d1ce251a6c (patch) | |
| tree | 982444f08fa1ebfd3e9aae3e03241d207a3fea8c | |
| parent | 23e6e57a93bcabe86d5f0eab1df0c44706ab18f3 (diff) | |
| download | linux-0e4c1eb59909ddaef19cd997e646d5d1ce251a6c.tar.xz | |
dm-verity-fec: warn even when there were no errors
Currently FEC logs a warning message if at least one error was
corrected, or an error message if there were uncorrectable errors.
However, it doesn't log anything if there were no errors.
"No errors" is actually unexpected, though, considering that dm-verity
calls verity_fec_decode() only when a block's digest doesn't match.
If there were to ever be a bug where verity_fec_decode() is called on
blocks with the correct digest, then there would be no indication in the
log that FEC is running and degrading performance.
Therefore, let's log the warning message even when there were no errors.
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
| -rw-r--r-- | drivers/md/dm-verity-fec.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/dm-verity-fec.c b/drivers/md/dm-verity-fec.c index fb71e83e6404..85ad9dc210ff 100644 --- a/drivers/md/dm-verity-fec.c +++ b/drivers/md/dm-verity-fec.c @@ -133,7 +133,7 @@ done: if (r < 0 && neras) DMERR_LIMIT("%s: FEC %llu: failed to correct: %d", v->data_dev->name, target_block, r); - else if (r == 0 && corrected > 0) + else if (r == 0) DMWARN_LIMIT("%s: FEC %llu: corrected %d errors", v->data_dev->name, target_block, corrected); |