DM RAID: Explicitly turn off bad block support
DM RAID does not currently use the bad block tracking available in
MD. 'badblocks.shift' must be set to '-1' in order to explicitly
tell MD not to perform bad block related functions, like
narrow_write_error().
Signed-off-by: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Index: linux-upstream/drivers/md/dm-raid.c
===================================================================
--- linux-upstream.orig/drivers/md/dm-raid.c
+++ linux-upstream/drivers/md/dm-raid.c
@@ -170,8 +170,10 @@ static struct raid_set *context_alloc(st
rs->md.delta_disks = 0;
rs->md.recovery_cp = 0;
- for (i = 0; i < raid_devs; i++)
+ for (i = 0; i < raid_devs; i++) {
md_rdev_init(&rs->dev[i].rdev);
+ rs->dev[i].rdev.badblocks.shift = -1; /* No bad block support */
+ }
/*
* Remaining items to be initialized by further RAID params:
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
