From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/3] f2fs: fix to avoid overflow while left shift operation
Date: Fri, 15 Aug 2025 16:40:09 +0000 [thread overview]
Message-ID: <175527600974.1161945.15609859403158896445.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250805062912.3070949-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 5 Aug 2025 14:29:10 +0800 you wrote:
> Should cast type of folio->index from pgoff_t to loff_t to avoid overflow
> while left shift operation.
>
> Fixes: 3265d3db1f16 ("f2fs: support partial truncation on compressed inode")
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/compress.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev,v3,1/3] f2fs: fix to avoid overflow while left shift operation
https://git.kernel.org/jaegeuk/f2fs/c/0fe1c6bec54e
- [f2fs-dev,v3,2/3] f2fs: fix to zero data after EOF for compressed file correctly
https://git.kernel.org/jaegeuk/f2fs/c/0b2cd5092139
- [f2fs-dev,v3,3/3] f2fs: clean up f2fs_truncate_partial_cluster()
https://git.kernel.org/jaegeuk/f2fs/c/cbba5038ee29
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-15 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 6:29 Chao Yu
2025-08-05 6:29 ` [PATCH v3 2/3] f2fs: fix to zero data after EOF for compressed file correctly Chao Yu
2025-08-05 6:29 ` [PATCH v3 3/3] f2fs: clean up f2fs_truncate_partial_cluster() Chao Yu
2025-08-15 16:40 ` patchwork-bot+f2fs [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=175527600974.1161945.15609859403158896445.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®