The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Xiaole He <hexiaole1994@126.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix age extent cache insertion skip on counter overflow
Date: Tue, 11 Nov 2025 22:50:27 +0000	[thread overview]
Message-ID: <176290142724.3596344.8108085156417902298.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251027092341.5011-1-hexiaole1994@126.com>

Hello:

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

On Mon, 27 Oct 2025 17:23:41 +0800 you wrote:
> The age extent cache uses last_blocks (derived from
> allocated_data_blocks) to determine data age. However, there's a
> conflict between the deletion
> marker (last_blocks=0) and legitimate last_blocks=0 cases when
> allocated_data_blocks overflows to 0 after reaching ULLONG_MAX.
> 
> In this case, valid extents are incorrectly skipped due to the
> "if (!tei->last_blocks)" check in __update_extent_tree_range().
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v2] f2fs: fix age extent cache insertion skip on counter overflow
    https://git.kernel.org/jaegeuk/f2fs/c/96d62153b64c

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



      parent reply	other threads:[~2025-11-11 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  3:54 [PATCH v1] f2fs: fix age extent cache insertion skip on counter overflow Xiaole He
2025-10-27  8:04 ` Chao Yu
2025-10-27  9:23 ` [PATCH v2] " Xiaole He
2025-10-27 10:55   ` Chao Yu
2025-11-11 22:50   ` 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=176290142724.3596344.8108085156417902298.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=hexiaole1994@126.com \
    --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