From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Zhan Xusheng <zhanxusheng@xiaomi.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix defragment writeback range truncation on 32-bit
Date: Sun, 11 Oct 2026 16:00:06 +0800 [thread overview]
Message-ID: <b76e45ca-b455-4c2f-82c8-abbb596acb86@kernel.org> (raw)
In-Reply-To: <20261005154954.2097054-1-zhanxusheng@xiaomi.com>
On 10/5/26 23:49, Zhan Xusheng wrote:
> f2fs_defragment_range() flushes the range it is about to defragment:
>
> filemap_write_and_wait_range(inode->i_mapping,
> pg_start << PAGE_SHIFT,
> (pg_end << PAGE_SHIFT) - 1);
>
> pg_start and pg_end are pgoff_t, 32 bits on 32-bit kernels, so both
> shifts are evaluated in 32 bits and truncated before they are widened to
> the loff_t parameters. pg_end is only capped by the file's page count,
> so for a file larger than 4 GiB the shift wraps.
>
> For a 5 GiB file pg_end is 1310720 and the range collapses from
> [0, 5 GiB) to [0, 1 GiB), leaving the rest of the dirty pages unwritten
> before the blocks are moved. For 8 GiB the shift yields 0, the minus one
> makes it (loff_t)-1, and the range becomes [0, LLONG_MAX].
>
> The matching call in f2fs_collapse_range() already casts:
>
> filemap_write_and_wait_range(inode->i_mapping,
> (loff_t)index << PAGE_SHIFT,
> ((loff_t)pg_end << PAGE_SHIFT) - 1);
>
> Do the same here. On i386 the shift changes from "shl $0xc,%ecx" to
> "shld", i.e. from a 32-bit shift to a double-precision one.
>
Cc: stable@kernel.org
> Fixes: d323d005ac4a ("f2fs: support file defragment")
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-10-11 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:49 [f2fs-dev] [PATCH] f2fs: fix defragment writeback range truncation on 32-bit Zhan Xusheng
2026-10-11 8:00 ` Chao Yu via Linux-f2fs-devel [this message]
2026-10-13 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=b76e45ca-b455-4c2f-82c8-abbb596acb86@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.