diff options
| author | Milan Broz <gmazyland@gmail.com> | 2019-06-20 13:00:19 +0200 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2019-06-25 14:09:14 -0400 |
| commit | 2eba4e640b2c4161e31ae20090a53ee02a518657 (patch) | |
| tree | ebc81485a4c4bbb56561e5a5aad266d8adf63289 | |
| parent | a0651926553cfe7992166432e418987760882652 (diff) | |
| download | linux-5.2.y-2eba4e640b2c4161e31ae20090a53ee02a518657.tar.gz | |
dm verity: use message limit for data block corruption message
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>
| -rw-r--r-- | drivers/md/dm-verity-target.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/md/dm-verity-target.c b/drivers/md/dm-verity-target.c index 720d06531aa30c..ea24ff0612e3a3 100644 --- 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); |