projects
/
linux-block.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
a065192
)
dm verity: use message limit for data block corruption message
author
Milan Broz
<gmazyland@gmail.com>
Thu, 20 Jun 2019 11:00:19 +0000
(13:00 +0200)
committer
Mike Snitzer
<snitzer@redhat.com>
Tue, 25 Jun 2019 18:09:14 +0000
(14:09 -0400)
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>
drivers/md/dm-verity-target.c
patch
|
blob
|
blame
|
history
diff --git
a/drivers/md/dm-verity-target.c
b/drivers/md/dm-verity-target.c
index 720d06531aa30c74ca1f52130e98a0531e512eb7..ea24ff0612e3a358c6aef10b4657f27f83fb9572 100644
(file)
--- a/
drivers/md/dm-verity-target.c
+++ b/
drivers/md/dm-verity-target.c
@@
-235,8
+235,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);