From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org, stable@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix the missing write pointer correction
Date: Fri, 28 Feb 2025 15:49:57 +0800 [thread overview]
Message-ID: <0e24eabc-c9e7-40c4-a793-b8ba6579cf77@kernel.org> (raw)
In-Reply-To: <20250227212401.152977-1-jaegeuk@kernel.org>
On 2025/2/28 5:24, Jaegeuk Kim via Linux-f2fs-devel wrote:
> If checkpoint was disabled, we missed to fix the write pointers.
>
> Cc: <stable@vger.kernel.org>
> Fixes: 1015035609e4 ("f2fs: fix changing cursegs if recovery fails on zoned device")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-02-28 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 21:24 [PATCH] f2fs: fix the missing write pointer correction Jaegeuk Kim
2025-02-28 7:49 ` Chao Yu [this message]
2025-02-28 16:30 ` [f2fs-dev] " patchwork-bot+f2fs
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=0e24eabc-c9e7-40c4-a793-b8ba6579cf77@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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