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: zone: fix to don't fail to grab GC target block on zoned device
Date: Mon, 19 Oct 2026 15:40:14 +0000 [thread overview]
Message-ID: <179242441406.2714099.11346194792931754269.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261019090032.1170825-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 19 Oct 2026 09:00:32 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> With out-of-memory fault injection (inject_type=0x0080800f) on a zoned
> device, f2fs stopped checkpoint during GC:
>
> F2FS-fs (dm-0): inject kmalloc in f2fs_kmalloc of move_data_block+0xc0b/0x12b0
> Workqueue: dm-1_zwplugs blk_zone_wplug_bio_work
> Call Trace:
> <TASK>
> dump_stack_lvl+0x4d/0x70
> f2fs_stop_checkpoint+0x1df/0x5d0
> f2fs_write_end_bio+0xdbb/0x1320
> blk_zone_wplug_bio_work+0x2aa/0x7d0
> process_one_work+0x5c6/0xde0
> worker_thread+0x403/0xb70
> kthread+0x235/0x2e0
> ret_from_fork+0x2f/0x70
> ret_from_fork_asm+0x1a/0x30
> </TASK>
> F2FS-fs (dm-0): Stopped filesystem due to reason: 3
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: zone: fix to don't fail to grab GC target block on zoned device
https://git.kernel.org/jaegeuk/f2fs/c/14f329117d10
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:[~2026-10-19 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 9:00 Chao Yu
2026-10-19 15: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=179242441406.2714099.11346194792931754269.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
all inboxes | Powered by JetHome®