BMC/Intel-BMC/linux.git/drivers/md/dm-thin-metadata.c, branch dev-4.6

dm thin metadata: don't issue prefetches if a transaction abort has failed

2016-03-10T22:12:09+00:00

If a transaction abort has failed then we can no longer use the metadata device. Typically this happens if the superblock is unreadable. This fix addresses a crash seen during metadata device failure testing. Fixes: 8a01a6af75 ("dm thin: prefetch missing metadata pages") Cc: stable@vger.kernel.org # 3.19+ Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer

dm thin metadata: remove needless newline from subtree_dec() DMERR message

2016-03-10T22:12:05+00:00

Signed-off-by: Mike Snitzer

dm thin metadata: make dm_thin_find_mapped_range() atomic

2015-12-10T15:38:55+00:00

Refactor dm_thin_find_mapped_range() so that it takes the read lock on the metadata's lock; rather than relying on finer grained locking that is pushed down inside dm_thin_find_next_mapped_block() and dm_thin_find_block(). Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer

dm thin metadata: speed up discard of partially mapped volumes

2015-12-10T15:30:56+00:00

Use dm_btree_lookup_next() to more quickly discard partially mapped volumes. Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer

dm thin metadata: fix bug when taking a metadata snapshot

2015-12-09T18:18:12+00:00

When you take a metadata snapshot the btree roots for the mapping and details tree need to have their reference counts incremented so they persist for the lifetime of the metadata snap. The roots being incremented were those currently written in the superblock, which could possibly be out of date if concurrent IO is triggering new mappings, breaking of sharing, etc. Fix this by performing a commit with the metadata lock held while taking a metadata snapshot. Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer Cc: stable@vger.kernel.org

dm thin metadata: fix bug in dm_thin_remove_range()

2015-12-02T18:26:49+00:00

dm_btree_remove_leaves() only unmaps a contiguous region so we need a loop, in __remove_range(), to handle ranges that contain multiple regions. A new btree function, dm_btree_lookup_next(), is introduced which is more efficiently able to skip over regions of the thin device which aren't mapped. __remove_range() uses dm_btree_lookup_next() for each iteration of __remove_range()'s loop. Also, improve description of dm_btree_remove_leaves(). Fixes: 6550f075 ("dm thin metadata: add dm_thin_remove_range()") Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer Cc: stable@vger.kernel.org # 4.1+

dm persistent data: eliminate unnecessary return values

2015-10-31T23:06:02+00:00

dm_bm_unlock and dm_tm_unlock return an integer value but the returned value is always 0. The calling code sometimes checks the return value and sometimes doesn't. Eliminate these unnecessary return values and also the checks for them. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer

dm thin metadata: delete btrees when releasing metadata snapshot

2015-08-12T14:42:51+00:00

The device details and mapping trees were just being decremented before. Now btree_del() is called to do a deep delete. Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer Cc: stable@vger.kernel.org

dm thin metadata: fix a race when entering fail mode

2015-06-11T21:13:06+00:00

In dm_thin_find_block() the ->fail_io flag was checked outside the metadata device's root_lock, causing dm_thin_find_block() to race with the setting of this flag. Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer

dm thin metadata: add dm_thin_remove_range()

2015-06-11T21:13:04+00:00

Removes a range of blocks from the btree. Signed-off-by: Joe Thornber Signed-off-by: Mike Snitzer