dm: fix limits initialization when there are no data devices
authorMike Christie <michaelc@cs.wisc.edu>
Fri, 1 Mar 2013 22:45:48 +0000 (22:45 +0000)
committerAlasdair G Kergon <agk@redhat.com>
Fri, 1 Mar 2013 22:45:48 +0000 (22:45 +0000)
commit87eb5b21d92a92ac2da3163039d62df88c2b8422
treeada6ec7e575e4b95a018ecbe023af135da2b639e
parent23cb21092eb9dcec9d3604b68d95192b79915890
dm: fix limits initialization when there are no data devices

dm_calculate_queue_limits will first reset the provided limits to
defaults using blk_set_stacking_limits; whereby defeating the purpose of
retaining the original live table's limits -- as was intended via commit
3ae706561637331aa578e52bb89ecbba5edcb7a9 ("dm: retain table limits when
swapping to new table with no devices").

Fix this improper limits initialization (in the no data devices case) by
avoiding the call to dm_calculate_queue_limits.

[patch header revised by Mike Snitzer]

Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Cc: stable@vger.kernel.org # v3.6+
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
drivers/md/dm.c