linux-toradex.git/drivers/md/dm-thin-metadata.c, branch v4.2.6

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

dm thin metadata: add dm_thin_find_mapped_range()

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

Retrieve the next run of contiguously mapped blocks.  Useful for working
out where to break up IO.

Signed-off-by: Joe Thornber 
Signed-off-by: Mike Snitzer

dm thin metadata: remove in-core 'read_only' flag

2015-05-29T18:18:59+00:00

Leverage the block manager's read_only flag instead of duplicating it;
access with new dm_bm_is_read_only() method.

Signed-off-by: Mike Snitzer

dm thin metadata: remove unused dm_pool_get_data_block_size()

2015-02-09T18:06:49+00:00

The thin-pool target doesn't display the data block size as part of
its table status, unlike the dm-cache target, so there is no need for
dm_pool_get_data_block_size().

This was found using cppcheck.

Signed-off-by: Rickard Strandqvist 
Signed-off-by: Mike Snitzer

dm thin: prefetch missing metadata pages

2014-11-10T20:25:27+00:00

Prefetch metadata at the start of the worker thread and then again every
128th bio processed from the deferred list.

Signed-off-by: Joe Thornber 
Signed-off-by: Mike Snitzer

dm thin metadata: change dm_thin_find_block to allow blocking, but not issuing, IO

2014-11-10T20:25:26+00:00

This change is a prerequisite for allowing metadata to be prefetched.

Signed-off-by: Joe Thornber 
Signed-off-by: Mike Snitzer

dm thin metadata: do not allow the data block size to change

2014-07-15T18:05:26+00:00

The block size for the thin-pool's data device must remained fixed for
the life of the thin-pool.  Disallow any attempt to change the
thin-pool's data block size.

It should be noted that attempting to change the data block size via
thin-pool table reload will be ignored as a side-effect of the thin-pool
handover that the thin-pool target does during thin-pool table reload.

Here is an example outcome of attempting to load a thin-pool table that
reduced the thin-pool's data block size from 1024K to 512K.

Before:
kernel: device-mapper: thin: 253:4: growing the data device from 204800 to 409600 blocks

After:
kernel: device-mapper: thin metadata: changing the data block size (from 2048 to 1024) is not supported
kernel: device-mapper: table: 253:4: thin-pool: Error creating metadata object
kernel: device-mapper: ioctl: error adding target to table

Signed-off-by: Mike Snitzer 
Acked-by: Joe Thornber 
Cc: stable@vger.kernel.org

dm: take care to copy the space map roots before locking the superblock

2014-03-27T20:56:23+00:00

In theory copying the space map root can fail, but in practice it never
does because we're careful to check what size buffer is needed.

But make certain we're able to copy the space map roots before
locking the superblock.

Signed-off-by: Joe Thornber 
Signed-off-by: Mike Snitzer 
Cc: stable@vger.kernel.org # drop dm-era and dm-cache changes as needed