diff options
author | Mike Snitzer <snitzer@redhat.com> | 2014-10-08 18:26:13 -0400 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2014-10-09 09:41:40 -0600 |
commit | b8839b8c55f3fdd60dc36abcda7e0266aff7985c (patch) | |
tree | 27372945d214df68a1f5e750399084642dbc04f9 /ipc/ipc_sysctl.c | |
parent | 9d8f0bcca6ffa024a822ce4ab1008ab663f06672 (diff) | |
download | linux-stable-b8839b8c55f3fdd60dc36abcda7e0266aff7985c.tar.gz linux-stable-b8839b8c55f3fdd60dc36abcda7e0266aff7985c.tar.bz2 linux-stable-b8839b8c55f3fdd60dc36abcda7e0266aff7985c.zip |
block: fix alignment_offset math that assumes io_min is a power-of-2
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>
Cc: stable@vger.kernel.org
Acked-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'ipc/ipc_sysctl.c')
0 files changed, 0 insertions, 0 deletions