From: Erich Eckner <g...@eckner.net>
Similar to f710126cfc89c8df477002a26dee8407eb0b4acd, this message should
also better identify the device with the integrity failure.
---
drivers/md/dm-integrity.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/md/dm-integrity.c b/drivers/md/dm-integrity.c
index b225b3e445fa..92f16315ee1b 100644
--- a/drivers/md/dm-integrity.c
+++ b/drivers/md/dm-integrity.c
@@ -1563,7 +1563,9 @@ static void integrity_metadata(struct work_struct *w)
checksums_ptr - checksums,
!dio->write ? TAG_CMP : TAG_WRITE);
if (unlikely(r)) {
if (r > 0) {
- DMERR_LIMIT("Checksum failed at sector
0x%llx",
+ char b[BDEVNAME_SIZE];
+ DMERR_LIMIT("%s: Checksum failed at
sector 0x%llx",
+ bio_devname(bio, b),
(unsigned long long)(sector
- ((r + ic->tag_size - 1) / ic->tag_size)));
r = -EILSEQ;
atomic64_inc(&ic->number_of_mismatches);
--
2.25.0
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
