android_kernel_oneplus_msm8998/fs/ext2
Jan Kara 64847df5bf ext2: Fix underflow in ext2_max_size()
commit 1c2d14212b15a60300a2d4f6364753e87394c521 upstream.

When ext2 filesystem is created with 64k block size, ext2_max_size()
will return value less than 0. Also, we cannot write any file in this fs
since the sb->maxbytes is less than 0. The core of the problem is that
the size of block index tree for such large block size is more than
i_blocks can carry. So fix the computation to count with this
possibility.

File size limits computed with the new function for the full range of
possible block sizes look like:

bits file_size
10     17247252480
11    275415851008
12   2196873666560
13   2197948973056
14   2198486220800
15   2198754754560
16   2198888906752

CC: stable@vger.kernel.org
Reported-by: yangerkun <yangerkun@huawei.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-03-23 08:44:36 +01:00
..
acl.c
acl.h
balloc.c
dir.c
ext2.h
file.c
ialloc.c
inode.c
ioctl.c
Kconfig
Makefile
namei.c do d_instantiate/unlock_new_inode combinations safely 2018-05-30 07:48:52 +02:00
super.c ext2: Fix underflow in ext2_max_size() 2019-03-23 08:44:36 +01:00
symlink.c
xattr.c ext2: fix potential use after free 2018-12-13 09:21:27 +01:00
xattr.h
xattr_security.c
xattr_trusted.c
xattr_user.c