From: Song Chen <chensong_2000@126.com>
To: arnd@arndb.de, kees@kernel.org, clm@fb.com, dsterba@suse.com
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: add error injection support for checksum verification
Date: Mon, 13 Jul 2026 09:00:00 +0800 [thread overview]
Message-ID: <98ed90ff-443d-455e-a991-95e2a8f8696d@126.com> (raw)
In-Reply-To: <20260702023638.8165-1-chensong_2000@126.com>
Dear Maintainers and Reviewers,
This is friendly ping on this patchset.
The motive is rational and the implementation is simple and clear,
what's more, no impact to any other function. I would appreciate it if
you could have a look and leave comments.
Best regards,
Song
On 7/2/26 10:36, Song Chen wrote:
> This patchset adds fault injection support for btrfs_data_csum_ok,
> enabling controlled simulation of checksum mismatches to test btrfs
> silent data corruption detection and reporting paths.
>
> The first patch extends the error injection framework with a new type,
> EI_ETYPE_FALSE, which allows bool-returning functions to be overridden
> with a false return value directly.
>
> The second patch marks btrfs_data_csum_ok with ALLOW_ERROR_INJECTION
> using this new type.
>
> Song Chen (2):
> error-injection: Introduce EI_ETYPE_FALSE for fail_function
> btrfs: Allow error injection on btrfs_data_csum_ok
>
> fs/btrfs/inode.c | 1 +
> include/asm-generic/error-injection.h | 1 +
> kernel/fail_function.c | 2 ++
> 3 files changed, 4 insertions(+)
>
prev parent reply other threads:[~2026-07-13 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 2:36 [PATCH 0/2] btrfs: add error injection support for checksum verification Song Chen
2026-07-02 2:36 ` [PATCH 1/2] error-injection: Introduce EI_ETYPE_FALSE for fail_function Song Chen
2026-07-02 2:36 ` [PATCH 2/2] btrfs: Allow error injection on btrfs_data_csum_ok Song Chen
2026-07-13 1:00 ` Song Chen [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=98ed90ff-443d-455e-a991-95e2a8f8696d@126.com \
--to=chensong_2000@126.com \
--cc=arnd@arndb.de \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=kees@kernel.org \
--cc=linux-arch@vger.kernel.org \
--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