From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 533583F4129 for ; Thu, 14 May 2026 23:31:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778801460; cv=none; b=oaMw1xVM3nyrMLSczJCd7DivZboto2E1l8b2dJ5Zxh2gFwh1SCBPlN0H3s72LlKC5vfLyy8kXFcjCHb/f/74G9n8k/JBhDeqDZObwjCXmGaS1OM+UKP+vm9J5I2osIf69WIuyZUIg3XH8oMc8uPVr17w2MeYKI4w8ZH4lsz40dY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778801460; c=relaxed/simple; bh=wKoY/Q5JQwc/3CahBN8P8WJGfZjwq89iaj6tdGfqlrI=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=qaBzuYn5iOLIq/3s07BaLw5HMgnJ8SSTn7evs6HN3br1R+DBuPA7KanmRyVjJZgbHuIIFPFuBHkhhcZ/+HKynI72oxRegVIidaqSA56EyEVXsiy+v816mGBktOQxtQa82uCM4BLkOjEp/HvpO+WoYQMFRO3ZLf8tIHDpP935utw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=L3XEkfwX; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="L3XEkfwX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DE930C2BCB3; Thu, 14 May 2026 23:30:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778801459; bh=wKoY/Q5JQwc/3CahBN8P8WJGfZjwq89iaj6tdGfqlrI=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=L3XEkfwXA0hSrc1gtg1e7fkQZ93jNUjQ6Wt4RPlmd3Fsxght3mX6PUmJo7lEwzF8m ZskgJqacsEWMUP0fBw+sOeIs1bDcMZzniRX/gOl4WHF5pReQVF+3buJhgLGI7CnbFQ DMyN/hCEDT6dgGYgcka78QiOFFuwDqmnsdiaevx4Q+RrpcZsEwhYKjgqdpCAxz61Pj R/68yxwnRqzBoA2Gwh5NWmdGnpUxAUT0wKwB7TbZdFBF0CeITveGQO/Kbn00YQ7JRO B8st+nFfgD9LV9zfNLhOpkI9k+UmcIIVooLTqHoA9DcT4yNQGGACgq+0ncVhVteoZi rHdrL7wXLEGjA== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id B9DE439E4DB3; Thu, 14 May 2026 23:30:05 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH] f2fs: optimize representative type determination in GC From: patchwork-bot+f2fs@kernel.org Message-Id: <177880140455.123857.24496031393456526.git-patchwork-notify@kernel.org> Date: Thu, 14 May 2026 23:30:04 +0000 References: <20260514205513.1464863-1-daeho43@gmail.com> In-Reply-To: <20260514205513.1464863-1-daeho43@gmail.com> To: Daeho Jeong Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com, daehojeong@google.com Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Thu, 14 May 2026 13:55:13 -0700 you wrote: > From: Daeho Jeong > > 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