mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yufen Yu <yuyufen@huawei.com>
To: <jaegeuk@kernel.org>, <chao@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>, <yuyufen@huawei.com>
Subject: [PATCH 0/5] f2fs: try to use common fault injection framework
Date: Fri, 1 Apr 2022 15:19:04 +0800	[thread overview]
Message-ID: <20220401071909.505086-1-yuyufen@huawei.com> (raw)

Hi,

  Kernel fault injection framework have provided a a systematic
  way to support error injection via debugfs in the /sys/kernel/debug
  directory.

  Compared to the current fault injection by mount options and sysfs,
  fault injection framework can provide more easy used fault injection
  control means.

  Thus, this patchset try to use common fault injection for f2fs.

Yufen Yu (5):
  f2fs: extract f2fs root debugfs to init_f2fs_fs
  f2fs: use common fault injection frmework
  f2fs: replace function time_to_inject by f2fs_should_fail
  f2fs: get rid of stale fault injection code
  f2fs: update doc for f2fs fault injection

 Documentation/filesystems/f2fs.rst | 118 ++++++++++++++++++++++-------
 fs/f2fs/Kconfig                    |   2 +-
 fs/f2fs/Makefile                   |   1 +
 fs/f2fs/checkpoint.c               |   4 +-
 fs/f2fs/data.c                     |   4 +-
 fs/f2fs/debug.c                    |  19 +----
 fs/f2fs/dir.c                      |   2 +-
 fs/f2fs/f2fs.h                     |  81 ++++++++------------
 fs/f2fs/fault_inject.c             |  67 ++++++++++++++++
 fs/f2fs/file.c                     |   2 +-
 fs/f2fs/gc.c                       |   2 +-
 fs/f2fs/inode.c                    |   2 +-
 fs/f2fs/node.c                     |   2 +-
 fs/f2fs/segment.c                  |   4 +-
 fs/f2fs/super.c                    |  82 ++++++--------------
 fs/f2fs/sysfs.c                    |  23 ------
 16 files changed, 227 insertions(+), 188 deletions(-)
 create mode 100644 fs/f2fs/fault_inject.c

-- 
2.31.1


             reply	other threads:[~2022-04-01  7:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  7:19 Yufen Yu [this message]
2022-04-01  7:19 ` [PATCH 1/5] f2fs: extract f2fs root debugfs to init_f2fs_fs Yufen Yu
2022-04-01  7:19 ` [PATCH 2/5] f2fs: use common fault injection frmework Yufen Yu
2022-04-01  7:19 ` [PATCH 3/5] f2fs: replace function time_to_inject by f2fs_should_fail Yufen Yu
2022-04-01  7:19 ` [PATCH 4/5] f2fs: get rid of stale fault injection code Yufen Yu
2022-04-01  8:28   ` [f2fs-dev] " Chao Yu
2022-04-06  3:01     ` Yufen Yu
2022-04-11 10:04       ` Chao Yu
2022-04-11 21:20         ` Jaegeuk Kim
2022-04-12 11:04           ` Yufen Yu
2022-04-19  2:56             ` Chao Yu
2022-04-01  7:19 ` [PATCH 5/5] f2fs: update doc for f2fs fault injection Yufen 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=20220401071909.505086-1-yuyufen@huawei.com \
    --to=yuyufen@huawei.com \
    --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

all inboxes | Powered by JetHome®