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] f2fs: fix to zero post-EOF data when extending file size
Date: Tue, 14 Jul 2026 03:00:11 +0000 [thread overview]
Message-ID: <178399801188.2939750.4882347111407604068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260706072606.3709384-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 6 Jul 2026 07:26:06 +0000 you wrote:
> generic/794 4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad)
> --- tests/generic/794.out 2026-06-12 08:46:32.766426241 +0800
> +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800
> @@ -1,4 +1,16 @@
> QA output created by 794
> append_write
> +FAIL: non-zero data in gap [4080,4096) after shutdown+remount
> +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a >ZZZZZZZZZZZZZZZZ<
> +*
> +001000
> truncate_up
> ...
> (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad' to see the entire diff)
> Ran: generic/794
> Failures: generic/794
> Failed 1 of 1 tests
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to zero post-EOF data when extending file size
https://git.kernel.org/jaegeuk/f2fs/c/7e097cad3ac1
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-07-14 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 7:26 [PATCH] f2fs: fix to zero post-EOF data when extending file size Chao Yu
2026-07-14 3:00 ` patchwork-bot+f2fs [this message]
2026-07-15 18:05 ` [f2fs-dev] " Jaegeuk Kim
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=178399801188.2939750.4882347111407604068.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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox