From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Milan Broz <gmazyland@gmail.com>,
Mike Snitzer <snitzer@redhat.com>,
Sasha Levin <sashal@kernel.org>
Subject: [PATCH AUTOSEL 4.4 6/6] dm verity: use message limit for data block corruption message
Date: Tue, 2 Jul 2019 22:18:58 -0400 [thread overview]
Message-ID: <20190703021858.18653-6-sashal@kernel.org> (raw)
In-Reply-To: <20190703021858.18653-1-sashal@kernel.org>
From: Milan Broz <gmazyland@gmail.com>
[ 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>
---
drivers/md/dm-verity.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/md/dm-verity.c b/drivers/md/dm-verity.c
index ccf41886ebcf..7054afd49f82 100644
--- a/drivers/md/dm-verity.c
+++ b/drivers/md/dm-verity.c
@@ -221,8 +221,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);
--
2.20.1
prev parent reply other threads:[~2019-07-03 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 2:18 [PATCH AUTOSEL 4.4 1/6] perf/core: Fix perf_sample_regs_user() mm check Sasha Levin
2019-07-03 2:18 ` [PATCH AUTOSEL 4.4 2/6] ARM: omap2: remove incorrect __init annotation Sasha Levin
2019-07-03 2:18 ` [PATCH AUTOSEL 4.4 3/6] be2net: fix link failure after ethtool offline test Sasha Levin
2019-07-03 2:18 ` [PATCH AUTOSEL 4.4 4/6] ppp: mppe: Add softdep to arc4 Sasha Levin
2019-07-03 2:18 ` [PATCH AUTOSEL 4.4 5/6] sis900: fix TX completion Sasha Levin
2019-07-03 2:18 ` Sasha Levin [this message]
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=20190703021858.18653-6-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=gmazyland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).