diff options
| author | Joe Thornber <ejt@redhat.com> | 2017-03-31 10:09:45 -0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2017-03-31 11:33:44 -0400 |
| commit | 449b668ce0b9069fcaafa6344c7f10fa2ba9632e (patch) | |
| tree | 6efb710aa1954bcb360f7562ea895b53ad5abf60 /drivers/md/dm-cache-target.c | |
| parent | 7b81ef8b14f80033e4a4168d199a0f5fd79b9426 (diff) | |
| download | linux-449b668ce0b9069fcaafa6344c7f10fa2ba9632e.tar.bz2 | |
dm cache: set/clear the cache core's dirty_bitset when loading mappings
When loading metadata make sure to set/clear the dirty bits in the cache
core's dirty_bitset as well as the policy.
Otherwise the cache core is unaware that any blocks were dirty when the
cache was last shutdown. A very serious side-effect being that the
cleaner policy would therefore never be tasked with writing back dirty
data from a cache that was in writeback mode (e.g. when switching from
smq policy to cleaner policy when decommissioning a writeback cache).
This fixes a serious data corruption bug associated with writeback mode.
Signed-off-by: Joe Thornber <ejt@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/md/dm-cache-target.c')
| -rw-r--r-- | drivers/md/dm-cache-target.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/md/dm-cache-target.c b/drivers/md/dm-cache-target.c index b7de289a10bb..6e747fcbdf0f 100644 --- a/drivers/md/dm-cache-target.c +++ b/drivers/md/dm-cache-target.c @@ -2960,6 +2960,12 @@ static int load_mapping(void *context, dm_oblock_t oblock, dm_cblock_t cblock, int r; struct cache *cache = context; + if (dirty) { + set_bit(from_cblock(cblock), cache->dirty_bitset); + atomic_inc(&cache->nr_dirty); + } else + clear_bit(from_cblock(cblock), cache->dirty_bitset); + r = policy_load_mapping(cache->policy, oblock, cblock, dirty, hint, hint_valid); if (r) return r; |