From: Christophe Vu-Brugier <cvubrugier@fastmail.fm>
To: linux-fsdevel@vger.kernel.org
Cc: Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Subject: [PATCH 0/1] exfat: fix i_blocks for files truncated over 4 GiB
Date: Thu, 18 Nov 2021 22:28:27 +0100 [thread overview]
Message-ID: <20211118212828.4360-1-cvubrugier@fastmail.fm> (raw)
From: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
The following patch fixes an issue in the exFAT driver. The number of
allocated blocks becomes wrong if a file is truncated over 4 GiB.
A similar issue was fixed last month by Sungjong Seo:
commit 0c336d6e33f4 ("exfat: fix incorrect loading of i_blocks for
large files")
Below is a test case for the issue. A 7 GiB file is truncated to 5 GiB
but stat() st_blocks shows only 1 GiB being used.
$ dd if=/dev/urandom of=file.bin bs=1024k count=7168
$ /sbin/xfs_io -c "stat" file.bin
fd.path = "file.bin"
fd.flags = non-sync,non-direct,read-write
stat.ino = 11
stat.type = regular file
stat.size = 7516192768
stat.blocks = 14680064
$ /sbin/xfs_io -c "truncate 5368709120" file.bin
$ /sbin/xfs_io -c "stat" file.bin
fd.path = "file.bin"
fd.flags = non-sync,non-direct,read-write
stat.ino = 11
stat.type = regular file
stat.size = 5368709120
stat.blocks = 2097152
Christophe Vu-Brugier (1):
exfat: fix i_blocks for files truncated over 4 GiB
fs/exfat/file.c | 2 +-
fs/exfat/super.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.33.0
next reply other threads:[~2021-11-18 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 21:28 Christophe Vu-Brugier [this message]
2021-11-18 21:28 ` [PATCH 1/1] exfat: fix i_blocks for files truncated over 4 GiB Christophe Vu-Brugier
2021-11-18 21:50 ` Matthew Wilcox
2021-11-18 22:43 ` Christophe Vu-Brugier
2021-11-19 17:37 ` [PATCH v2] " Christophe Vu-Brugier
2021-11-22 2:10 ` Sungjong Seo
2021-11-22 2:33 ` Namjae Jeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211118212828.4360-1-cvubrugier@fastmail.fm \
--to=cvubrugier@fastmail.fm \
--cc=christophe.vu-brugier@seagate.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).