dm thin: re-establish read-only state when switching to fail mode
authorJoe Thornber <ejt@redhat.com>
Wed, 4 Dec 2013 21:30:01 +0000 (16:30 -0500)
committerMike Snitzer <snitzer@redhat.com>
Tue, 10 Dec 2013 21:35:12 +0000 (16:35 -0500)
commit5383ef3a929a1366e2ced45cd6d74be7aa2a2281
tree263f0b025cdedad9ac4ea151a8fa0f25093682f8
parent020cc3b5e28c2e24f59f53a9154faf08564f308e
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
drivers/md/dm-thin.c