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-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag
Date: Tue, 24 Mar 2026 17:32:11 +0000 [thread overview]
Message-ID: <177437353128.1223048.4639198904019180546.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260323083834.156393-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 23 Mar 2026 16:38:32 +0800 you wrote:
> f2fs_handle_page_eio() is the only left place we set CP_ERROR_FLAG
> directly, it missed to update superblock.s_stop_reason, let's
> call f2fs_handle_critical_error() instead to fix that.
>
> Introduce STOP_CP_REASON_READ_{META,NODE,DATA} stop_cp_reason enum
> variable to indicate which kind of data we failed to read.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag
https://git.kernel.org/jaegeuk/f2fs/c/bd882ffdd48a
- [f2fs-dev,v3,2/2] f2fs: use more generic f2fs_stop_checkpoint()
https://git.kernel.org/jaegeuk/f2fs/c/be09d78b6d54
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag
Date: Tue, 24 Mar 2026 17:32:11 +0000 [thread overview]
Message-ID: <177437353128.1223048.4639198904019180546.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260323083834.156393-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 23 Mar 2026 16:38:32 +0800 you wrote:
> f2fs_handle_page_eio() is the only left place we set CP_ERROR_FLAG
> directly, it missed to update superblock.s_stop_reason, let's
> call f2fs_handle_critical_error() instead to fix that.
>
> Introduce STOP_CP_REASON_READ_{META,NODE,DATA} stop_cp_reason enum
> variable to indicate which kind of data we failed to read.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag
https://git.kernel.org/jaegeuk/f2fs/c/bd882ffdd48a
- [f2fs-dev,v3,2/2] f2fs: use more generic f2fs_stop_checkpoint()
https://git.kernel.org/jaegeuk/f2fs/c/be09d78b6d54
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-03-24 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 8:38 [f2fs-dev] [PATCH v3 1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag Chao Yu via Linux-f2fs-devel
2026-03-23 8:38 ` Chao Yu
2026-03-23 8:38 ` [f2fs-dev] [PATCH v3 2/2] f2fs: use more generic f2fs_stop_checkpoint() Chao Yu via Linux-f2fs-devel
2026-03-23 8:38 ` Chao Yu
2026-03-24 17:32 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-03-24 17:32 ` [f2fs-dev] [PATCH v3 1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag 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=177437353128.1223048.4639198904019180546.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 \
/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.