From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v5 1/2] f2fs: fix to off-by-one issue in f2fs_zero_post_eof_page()
Date: Wed, 12 Aug 2026 20:30:06 +0000 [thread overview]
Message-ID: <178656660663.2090005.4601812465227179093.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811071637.4176024-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Aug 2026 15:16:36 +0800 you wrote:
> Otherwise, it will drop one more page after new_size which is not
> necessary.
>
> Cc: stable@kernel.org
> Fixes: ba8dac350faf ("f2fs: fix to zero post-eof page")
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v5,1/2] f2fs: fix to off-by-one issue in f2fs_zero_post_eof_page()
https://git.kernel.org/jaegeuk/f2fs/c/b2205d3cfd6c
- [f2fs-dev,v5,2/2] f2fs: fix to zero post-EOF data when extending file size
https://git.kernel.org/jaegeuk/f2fs/c/5eced87b7d19
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, stable@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v5 1/2] f2fs: fix to off-by-one issue in f2fs_zero_post_eof_page()
Date: Wed, 12 Aug 2026 20:30:06 +0000 [thread overview]
Message-ID: <178656660663.2090005.4601812465227179093.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811071637.4176024-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Aug 2026 15:16:36 +0800 you wrote:
> Otherwise, it will drop one more page after new_size which is not
> necessary.
>
> Cc: stable@kernel.org
> Fixes: ba8dac350faf ("f2fs: fix to zero post-eof page")
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v5,1/2] f2fs: fix to off-by-one issue in f2fs_zero_post_eof_page()
https://git.kernel.org/jaegeuk/f2fs/c/b2205d3cfd6c
- [f2fs-dev,v5,2/2] f2fs: fix to zero post-EOF data when extending file size
https://git.kernel.org/jaegeuk/f2fs/c/5eced87b7d19
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-08-12 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 7:16 [PATCH v5 1/2] f2fs: fix to off-by-one issue in f2fs_zero_post_eof_page() Chao Yu
2026-08-11 7:16 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-11 7:16 ` [PATCH v5 2/2] f2fs: fix to zero post-EOF data when extending file size Chao Yu
2026-08-11 7:16 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-12 20:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-08-12 20:30 ` [f2fs-dev] [PATCH v5 1/2] f2fs: fix to off-by-one issue in f2fs_zero_post_eof_page() patchwork-bot+f2fs
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=178656660663.2090005.4601812465227179093.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@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 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.