summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorHeinz Mauelshagen <heinzm@redhat.com>2017-12-13 17:13:18 +0100
committerMike Snitzer <snitzer@redhat.com>2017-12-13 11:52:02 -0500
commit11e4723206683ad59f8e9dc7771e7b44a37f7b62 (patch)
tree0ef98a68bb0a8722a4765eac7be2fb3204fa8c92 /kernel
parent53bf5384f9b9e37c628f171366959a38c89779ca (diff)
downloadlinux-11e4723206683ad59f8e9dc7771e7b44a37f7b62.tar.bz2
dm raid: stop keeping raid set frozen altogether
In order to avoid redoing synchronization/recovery/reshape partially, the raid set got frozen until after all passed in table line flags had been cleared. The related table reload sequence had to be precisely followed, or reshaping may lead to data corruption caused by the active mapping carrying on with a reshape when the inactive mapping already had retrieved a stale reshape position. Harden by retrieving the actual resync/recovery/reshape position during resume whilst the active table is suspended thus avoiding to keep the raid set frozen altogether. This prevents superfluous redoing of an already resynchronized or recovered segment and, most importantly, potential for redoing of an already reshaped segment causing data corruption. Fixes: d39f0010e ("dm raid: fix raid_resume() to keep raid set frozen as needed") Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions