diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2014-10-08 18:26:13 -0400 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2014-12-14 16:23:47 +0000 |
| commit | 5c250851e1f7850dfe765ff8f6d04ef4ce6e19a7 (patch) | |
| tree | 9af55862b03ee366c8e160ce06b2d371f14a1861 /block/blk-integrity.c | |
| parent | a59a6d8aad7120f8cf6b2393d2a1463de0c1ba6c (diff) | |
| download | kernel_samsung_smdk4412-5c250851e1f7850dfe765ff8f6d04ef4ce6e19a7.zip kernel_samsung_smdk4412-5c250851e1f7850dfe765ff8f6d04ef4ce6e19a7.tar.gz kernel_samsung_smdk4412-5c250851e1f7850dfe765ff8f6d04ef4ce6e19a7.tar.bz2 | |
block: fix alignment_offset math that assumes io_min is a power-of-2
commit b8839b8c55f3fdd60dc36abcda7e0266aff7985c upstream.
The math in both blk_stack_limits() and queue_limit_alignment_offset()
assume that a block device's io_min (aka minimum_io_size) is always a
power-of-2. Fix the math such that it works for non-power-of-2 io_min.
This issue (of alignment_offset != 0) became apparent when testing
dm-thinp with a thinp blocksize that matches a RAID6 stripesize of
1280K. Commit fdfb4c8c1 ("dm thin: set minimum_io_size to pool's data
block size") unlocked the potential for alignment_offset != 0 due to
the dm-thin-pool's io_min possibly being a non-power-of-2.
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: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'block/blk-integrity.c')
0 files changed, 0 insertions, 0 deletions