dm space map common: make sure new space is used during extend
authorJoe Thornber <ejt@redhat.com>
Tue, 7 Jan 2014 15:47:59 +0000 (15:47 +0000)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 1 Apr 2014 23:58:41 +0000 (00:58 +0100)
commitda159c8e81382a7fd65d0d6a612999aecfaf4ca5
tree6ed77c154353e4bdbee003da4d35b1536d94d55b
parent1765b496a0a8b2d8d9c840fa748986f0ca93198f
dm space map common: make sure new space is used during extend

commit 12c91a5c2d2a8e8cc40a9552313e1e7b0a2d9ee3 upstream.

When extending a low level space map we should update nr_blocks at
the start so the new space is used for the index entries.

Otherwise extend can fail, e.g.: sm_metadata_extend call sequence
that fails:
 -> sm_ll_extend
    -> dm_tm_new_block -> dm_sm_new_block -> sm_bootstrap_new_block
    => returns -ENOSPC because smm->begin == smm->ll.nr_blocks

Signed-off-by: Joe Thornber <ejt@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/md/persistent-data/dm-space-map-common.c