From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: jaegeuk@kernel.org, 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: Tue, 13 Oct 2026 22:30:33 +0000 [thread overview]
Message-ID: <179193063351.1493834.17419518506732604429.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005154954.2097054-1-zhanxusheng@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 5 Oct 2026 23:49:54 +0800 you 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix defragment writeback range truncation on 32-bit
https://git.kernel.org/jaegeuk/f2fs/c/92154fe28c37
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-10-13 22:30 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
2026-10-13 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
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=179193063351.1493834.17419518506732604429.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.