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] f2fs: fix to bail out in get_new_segment()
Date: Mon, 28 Apr 2025 22:40:59 +0000 [thread overview]
Message-ID: <174588005948.1067750.7393632112050436477.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250422115638.123455-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 22 Apr 2025 19:56:38 +0800 you wrote:
> ------------[ cut here ]------------
> WARNING: CPU: 3 PID: 579 at fs/f2fs/segment.c:2832 new_curseg+0x5e8/0x6dc
> pc : new_curseg+0x5e8/0x6dc
> Call trace:
> new_curseg+0x5e8/0x6dc
> f2fs_allocate_data_block+0xa54/0xe28
> do_write_page+0x6c/0x194
> f2fs_do_write_node_page+0x38/0x78
> __write_node_page+0x248/0x6d4
> f2fs_sync_node_pages+0x524/0x72c
> f2fs_write_checkpoint+0x4bc/0x9b0
> __checkpoint_and_complete_reqs+0x80/0x244
> issue_checkpoint_thread+0x8c/0xec
> kthread+0x114/0x1bc
> ret_from_fork+0x10/0x20
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to bail out in get_new_segment()
https://git.kernel.org/jaegeuk/f2fs/c/9cada264501c
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-04-28 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 11:56 [PATCH] f2fs: fix to bail out in get_new_segment() Chao Yu
2025-04-28 22: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=174588005948.1067750.7393632112050436477.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