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 v2 1/2] f2fs: add a proc entry show inject stats
Date: Thu, 10 Apr 2025 04:10:34 +0000 [thread overview]
Message-ID: <174425823476.3146257.16619631062841973924.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250320022230.1938110-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 20 Mar 2025 10:22:29 +0800 you wrote:
> This patch adds a proc entry named inject_stats to show total injected
> count for each fault type.
>
> cat /proc/fs/f2fs/<dev>/inject_stats
> fault_type injected_count
> kmalloc 0
> kvmalloc 0
> page alloc 0
> page get 0
> alloc bio(obsolete) 0
> alloc nid 0
> orphan 0
> no more block 0
> too big dir depth 0
> evict_inode fail 0
> truncate fail 0
> read IO error 0
> checkpoint error 0
> discard error 0
> write IO error 0
> slab alloc 0
> dquot initialize 0
> lock_op 0
> invalid blkaddr 0
> inconsistent blkaddr 0
> no free segment 0
> inconsistent footer 0
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: add a proc entry show inject stats
https://git.kernel.org/jaegeuk/f2fs/c/e073e9278983
- [f2fs-dev,v2,2/2] f2fs: fix to update injection attrs according to fault_option
https://git.kernel.org/jaegeuk/f2fs/c/2be96c2147e2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-10 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 2:22 [PATCH v2 1/2] f2fs: add a proc entry show inject stats Chao Yu
2025-03-20 2:22 ` [PATCH v2 2/2] f2fs: fix to update injection attrs according to fault_option Chao Yu
2025-03-20 3:32 ` [f2fs-dev] [PATCH v2 1/2] f2fs: add a proc entry show inject stats Zhiguo Niu
2025-04-10 4:10 ` 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=174425823476.3146257.16619631062841973924.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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