block: fix blk_integrity_register to use template's interval_exp if not 0
authorMike Snitzer <snitzer@redhat.com>
Sat, 22 Apr 2017 21:22:09 +0000 (17:22 -0400)
committerJens Axboe <axboe@fb.com>
Sun, 23 Apr 2017 18:59:56 +0000 (12:59 -0600)
commit2859323e35ab5fc42f351fbda23ab544eaa85945
tree40e05f23fc5a9bbae5d1a44e5935eaa30cbf0243
parent659226eb630ff522b30d8b8a82c9e722756e6bd4
block: fix blk_integrity_register to use template's interval_exp if not 0

When registering an integrity profile: if the template's interval_exp is
not 0 use it, otherwise use the ilog2() of logical block size of the
provided gendisk.

This fixes a long-standing DM linear target bug where it cannot pass
integrity data to the underlying device if its logical block size
conflicts with the underlying device's logical block size.

Cc: stable@vger.kernel.org
Reported-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Acked-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
block/blk-integrity.c