exfat: fix i_blocks for files truncated over 4 GiB
authorChristophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Mon, 22 Nov 2021 13:02:37 +0000 (22:02 +0900)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 8 Mar 2022 18:12:32 +0000 (19:12 +0100)
commitc9f727219f3e64b63e03e00dc0cf3d685c17f730
tree4face734f81537859434f31fa77901db8b4f5fea
parent1ffc130388c5065d491ca58fb41bc248fd63a2f5
exfat: fix i_blocks for files truncated over 4 GiB

[ Upstream commit 92fba084b79e6bc7b12fc118209f1922c1a2df56 ]

In exfat_truncate(), the computation of inode->i_blocks is wrong if
the file is larger than 4 GiB because a 32-bit variable is used as a
mask. This is fixed and simplified by using round_up().

Also fix the same buggy computation in exfat_read_root() and another
(correct) one in exfat_fill_inode(). The latter was fixed another way
last month but can be simplified by using round_up() as well. See:

  commit 0c336d6e33f4 ("exfat: fix incorrect loading of i_blocks for
                        large files")

Fixes: 98d917047e8b ("exfat: add file operations")
Cc: stable@vger.kernel.org # v5.7+
Suggested-by: Matthew Wilcox <willy@infradead.org>
Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com>
Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/exfat/file.c
fs/exfat/inode.c
fs/exfat/super.c