summaryrefslogtreecommitdiff
path: root/tools/pcmcia
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2017-10-07 22:36:49 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-11-08 09:08:34 (GMT)
commit0e9deca480c30d78c0b922bff9abe2f81284d8fc (patch)
treeb361eaf60a7718d1ec219c50aaaa9c1d47b81703 /tools/pcmcia
parenta418b2fd8e53bc297288f6dcd5e8ea37297f3e70 (diff)
downloadlinux-0e9deca480c30d78c0b922bff9abe2f81284d8fc.tar.xz
ext4: fix stripe-unaligned allocations
[ Upstream commit d9b22cf9f5466a057f2a4f1e642b469fa9d73117 ] When a filesystem is created using: mkfs.ext4 -b 4096 -E stride=512 <dev> and we try to allocate 64MB extent, we will end up directly in ext4_mb_complex_scan_group(). This is because the request is detected as power-of-two allocation (so we start in ext4_mb_regular_allocator() with ac_criteria == 0) however the check before ext4_mb_simple_scan_group() refuses the direct buddy scan because the allocation request is too large. Since cr == 0, the check whether we should use ext4_mb_scan_aligned() fails as well and we fall back to ext4_mb_complex_scan_group(). Fix the problem by checking for upper limit on power-of-two requests directly when detecting them. Reported-by: Ross Zwisler <ross.zwisler@linux.intel.com> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/pcmcia')
0 files changed, 0 insertions, 0 deletions