The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
	daehojeong@google.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: optimize representative type determination in GC
Date: Thu, 14 May 2026 23:30:04 +0000	[thread overview]
Message-ID: <177880140455.123857.24496031393456526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260514205513.1464863-1-daeho43@gmail.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Thu, 14 May 2026 13:55:13 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
> 
> In large section mode, do_garbage_collect() previously determined the
> section's representative type by looking only at the first segment of
> the section. However, if data was fsynced into an area previously used
> as a node section, and this area is recovered during roll-forward
> recovery after sudden power off (SPO), GC would incorrectly assume the
> section's type based on an empty or obsolete first segment. This caused
> the recovered data segment to be misunderstood as being stuck inside a
> node section, triggering false inconsistency panics (Inconsistent
> segment type in SSA and SIT) and subsequent mount failures.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: optimize representative type determination in GC
    https://git.kernel.org/jaegeuk/f2fs/c/f8f9d0045df5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-05-14 23:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 20:55 [PATCH] f2fs: optimize representative type determination in GC Daeho Jeong
2026-05-14 23: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=177880140455.123857.24496031393456526.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=kernel-team@android.com \
    --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