From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, daehojeong@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid migrating empty section
Date: Mon, 29 Sep 2025 22:30:20 +0000 [thread overview]
Message-ID: <175918502025.1733438.16761795407237847575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250901020416.2172182-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 1 Sep 2025 10:04:15 +0800 you wrote:
> It reports a bug from device w/ zufs:
>
> F2FS-fs (dm-64): Inconsistent segment (173822) type [1, 0] in SSA and SIT
> F2FS-fs (dm-64): Stopped filesystem due to reason: 4
>
> Thread A Thread B
> - f2fs_expand_inode_data
> - f2fs_allocate_pinning_section
> - f2fs_gc_range
> - do_garbage_collect w/ segno #x
> - writepage
> - f2fs_allocate_data_block
> - new_curseg
> - allocate segno #x
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid migrating empty section
https://git.kernel.org/jaegeuk/f2fs/c/d625a2b08c08
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-09-29 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 2:04 Chao Yu
2025-09-03 0:04 ` [f2fs-dev] " Zhiguo Niu
2025-09-03 1:33 ` Chao Yu
2025-09-03 1:56 ` Zhiguo Niu
2025-09-29 22:30 ` 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=175918502025.1733438.16761795407237847575.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--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
Powered by JetHome