summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMilan Broz2019-06-20 13:00:19 +0200
committerGreg Kroah-Hartman2019-07-21 09:03:08 +0200
commit136847140cc891a875fce5cfdc4886eacfe1f767 (patch)
tree51b10947af87d16be77622dfd05c09d83f90d27e
parentdm table: don't copy from a NULL pointer in realloc_argv() (diff)
downloadkernel-qcow2-linux-136847140cc891a875fce5cfdc4886eacfe1f767.tar.gz
kernel-qcow2-linux-136847140cc891a875fce5cfdc4886eacfe1f767.tar.xz
kernel-qcow2-linux-136847140cc891a875fce5cfdc4886eacfe1f767.zip
dm verity: use message limit for data block corruption message
[ Upstream commit 2eba4e640b2c4161e31ae20090a53ee02a518657 ] DM verity should also use DMERR_LIMIT to limit repeat data block corruption messages. Signed-off-by: Milan Broz <gmazyland@gmail.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
-rw-r--r--drivers/md/dm-verity-target.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/md/dm-verity-target.c b/drivers/md/dm-verity-target.c
index fc65f0dedf7f..e3599b43f9eb 100644
--- a/drivers/md/dm-verity-target.c
+++ b/drivers/md/dm-verity-target.c
@@ -236,8 +236,8 @@ static int verity_handle_err(struct dm_verity *v, enum verity_block_type type,
BUG();
}
- DMERR("%s: %s block %llu is corrupted", v->data_dev->name, type_str,
- block);
+ DMERR_LIMIT("%s: %s block %llu is corrupted", v->data_dev->name,
+ type_str, block);
if (v->corrupted_errs == DM_VERITY_MAX_CORRUPTED_ERRS)
DMERR("%s: reached maximum errors", v->data_dev->name);