From: Chao Yu <chao@kernel.org>
To: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <chao@kernel.org>, David Disseldorp <ddiss@suse.de>
Subject: [PATCH v3 2/6] common/config: export F2FS_INJECT_PROG
Date: Tue, 11 Mar 2025 16:04:26 +0800 [thread overview]
Message-ID: <20250311080430.3696582-2-chao@kernel.org> (raw)
In-Reply-To: <20250311080430.3696582-1-chao@kernel.org>
export F2FS_INJECT_PROG w/ inject.f2fs, it can be used for fault injection.
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: David Disseldorp <ddiss@suse.de>
Signed-off-by: Chao Yu <chao@kernel.org>
---
v3:
- no changes
common/config | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/config b/common/config
index aa525825..7d017a05 100644
--- a/common/config
+++ b/common/config
@@ -316,6 +316,7 @@ export MKFS_BTRFS_PROG=$(set_mkfs_prog_path_with_opts btrfs)
export MKFS_F2FS_PROG=$(set_mkfs_prog_path_with_opts f2fs)
export DUMP_F2FS_PROG=$(type -P dump.f2fs)
export F2FS_IO_PROG=$(type -P f2fs_io)
+export F2FS_INJECT_PROG=$(type -P inject.f2fs)
export BTRFS_UTIL_PROG=$(type -P btrfs)
export BTRFS_SHOW_SUPER_PROG=$(type -P btrfs-show-super)
export BTRFS_CONVERT_PROG=$(type -P btrfs-convert)
--
2.48.1
next prev parent reply other threads:[~2025-03-11 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 8:04 [PATCH v3 1/6] common/config: remove redundant export variables Chao Yu
2025-03-11 8:04 ` Chao Yu [this message]
2025-03-11 8:04 ` [PATCH v3 3/6] common/config: export F2FS_FSCK_PROG Chao Yu
2025-03-11 14:09 ` Zorro Lang
2025-03-11 8:04 ` [PATCH v3 4/6] common/rc: use -f for mkfs.f2fs by default Chao Yu
2025-03-11 14:10 ` Zorro Lang
2025-03-11 8:04 ` [PATCH v3 5/6] common/rc: introduce _check_f2fs_filesystem() Chao Yu
2025-03-11 13:54 ` Zorro Lang
2025-03-11 8:04 ` [PATCH v3 6/6] f2fs/009: detect and repair nlink corruption Chao Yu
2025-03-11 9:20 ` Chao Yu
2025-03-11 14:06 ` Zorro Lang
2025-03-12 7:14 ` Chao Yu
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=20250311080430.3696582-2-chao@kernel.org \
--to=chao@kernel.org \
--cc=ddiss@suse.de \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@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