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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 20 May 2017 12:28:36 +0000 (14:28 +0200)
commit9b2fb8ad5ba1b528e2f2927898403b0df40fd09b
tree88963dbafe4f8abc1dba43db81d5a370d1aa5a10
parent884ba252f3f16c577d7e5f6996c3e73a834b19fe
block: fix blk_integrity_register to use template's interval_exp if not 0

commit 2859323e35ab5fc42f351fbda23ab544eaa85945 upstream.

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.

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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
block/blk-integrity.c