From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: liujinbao1 <jinbaoliu365@gmail.com>
Cc: jaegeuk@kernel.org, shengyong1@xiaomi.com, liujinbao1@xiaomi.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: Add trace_f2fs_fault_report
Date: Mon, 11 May 2026 01:50:04 +0000 [thread overview]
Message-ID: <177846420430.1981547.4906215813884027969.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260506095731.1039356-1-jinbaoliu365@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 6 May 2026 17:57:31 +0800 you wrote:
> From: liujinbao1 <liujinbao1@xiaomi.com>
>
> Add trace_f2fs_fault_report to trigger reporting upon f2fs_bug_on,
> need_fsck, stop_checkpoint, and handle_eio. Since f2fs_bug_on and
> need_fsck can be triggered in hundreds of scenarios, define set_sbi_flag
> as a macro to help capture the effective fault function and line number.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: Add trace_f2fs_fault_report
https://git.kernel.org/jaegeuk/f2fs/c/99c73d70fcdf
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-05-11 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 9:57 [f2fs-dev] [PATCH v3] f2fs: Add trace_f2fs_fault_report liujinbao1
2026-05-09 8:54 ` Chao Yu via Linux-f2fs-devel
2026-05-11 1:50 ` 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=177846420430.1981547.4906215813884027969.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=jinbaoliu365@gmail.com \
--cc=liujinbao1@xiaomi.com \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=shengyong1@xiaomi.com \
/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