From: thomas.tai@oracle.com (Thomas Tai)
Subject: [PATCH v4 0/2] nvme: Add fault injection feature
Date: Thu, 8 Feb 2018 13:38:28 -0500 [thread overview]
Message-ID: <1518115110-15930-1-git-send-email-thomas.tai@oracle.com> (raw)
Linux's fault injection framework provides a systematic way to support
error injection via debugfs in the /sys/kernel/debug directory. This
patch uses the framework to add error injection to NVMe driver.
Change log since last version:
from v3 to v4:
- correct documentation to cover status code can be changed
via debugfs
- add Reviewed-by: Keith Busch <keith.busch at intel.com>
from v1 to V2:
- add user changable status and no_retry debugfs attribute
- add document to show how to use nvme fault injection
from v0 to V1:
- move error injection point into nvme_end_request()
- Add expected result in the commit log
Thank you,
Thomas
next reply other threads:[~2018-02-08 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 18:38 Thomas Tai [this message]
2018-02-08 18:38 ` [PATCH v4 1/2] nvme: Add fault injection feature Thomas Tai
2018-02-08 18:38 ` [PATCH v4 2/2] Documentation: nvme: Documentation for nvme fault injection Thomas Tai
2018-02-11 10:09 ` [PATCH v4 0/2] nvme: Add fault injection feature Sagi Grimberg
2018-02-12 16:46 ` Thomas Tai
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=1518115110-15930-1-git-send-email-thomas.tai@oracle.com \
--to=thomas.tai@oracle.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