aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoe Thornber <ejt@redhat.com>2013-12-04 16:30:01 -0500
committerMike Snitzer <snitzer@redhat.com>2013-12-10 16:35:12 -0500
commit5383ef3a929a1366e2ced45cd6d74be7aa2a2281 (patch)
tree263f0b025cdedad9ac4ea151a8fa0f25093682f8
parent020cc3b5e28c2e24f59f53a9154faf08564f308e (diff)
dm thin: re-establish read-only state when switching to fail mode
If the thin-pool transitioned to fail mode and the thin-pool's table were reloaded for some reason: the new table's default pool mode would be read-write, though it will transition to fail mode during resume. When the pool mode transitions directly from PM_WRITE to PM_FAIL we need to re-establish the intermediate read-only state in both the metadata and persistent-data block manager (as is usually done with the normal pool mode transition sequence: PM_WRITE -> PM_READ_ONLY -> PM_FAIL). Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Cc: stable@vger.kernel.org
-rw-r--r--drivers/md/dm-thin.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/dm-thin.c b/drivers/md/dm-thin.c
index af79bae5ab74..0d7852e2b275 100644
--- a/drivers/md/dm-thin.c
+++ b/drivers/md/dm-thin.c
@@ -1400,6 +1400,7 @@ static void set_pool_mode(struct pool *pool, enum pool_mode mode)
1400 case PM_FAIL: 1400 case PM_FAIL:
1401 DMERR("%s: switching pool to failure mode", 1401 DMERR("%s: switching pool to failure mode",
1402 dm_device_name(pool->pool_md)); 1402 dm_device_name(pool->pool_md));
1403 dm_pool_metadata_read_only(pool->pmd);
1403 pool->process_bio = process_bio_fail; 1404 pool->process_bio = process_bio_fail;
1404 pool->process_discard = process_bio_fail; 1405 pool->process_discard = process_bio_fail;
1405 pool->process_prepared_mapping = process_prepared_mapping_fail; 1406 pool->process_prepared_mapping = process_prepared_mapping_fail;