From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to check continuousness in f2fs_sync_meta_pages() correctly
Date: Tue, 13 Oct 2026 22:30:35 +0000 [thread overview]
Message-ID: <179193063501.1493834.9099224335687107412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001000616.3824366-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 1 Oct 2026 00:06:16 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> In f2fs_sync_meta_pages(), whenever i becomes zero inside while loop,
> below check may be skipped, it failed to check the continuousness:
>
> if (nr_to_write != LONG_MAX && i != 0 &&
> folio->index != prev +
> folio_nr_pages(fbatch.folios[i-1])) {
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to check continuousness in f2fs_sync_meta_pages() correctly
https://git.kernel.org/jaegeuk/f2fs/c/1383cff4ccf3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-10-13 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 0:06 [f2fs-dev] [PATCH] f2fs: fix to check continuousness in f2fs_sync_meta_pages() correctly Chao Yu via Linux-f2fs-devel
2026-10-13 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=179193063501.1493834.9099224335687107412.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.