diff options
| author | Mohamed Khalfella <mkhalfella@purestorage.com> | 2026-08-11 16:11:52 -0700 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2026-08-19 07:51:23 -0700 |
| commit | 58e7c13c8f0468bdf7e10151d3fb556c6015ab2e (patch) | |
| tree | d0e2225eb17c030604d87d6debb3ab77dd87b2c5 /scripts | |
| parent | 56e1c6bbe4bb084d7ecf61698afdf70be23dd35f (diff) | |
| download | linux-58e7c13c8f0468bdf7e10151d3fb556c6015ab2e.tar.gz linux-58e7c13c8f0468bdf7e10151d3fb556c6015ab2e.zip | |
nvme: add opcode filtering for fault injection
Currently NVMe fault injection applies to every command routed through
nvme_should_fail(), which makes it hard to target a specific command
type when reproducing an issue in error-handling paths.
Add an "opcode" debugfs attribute alongside the existing "status" and
"dont_retry" knobs. It defaults to 0xffff, meaning "match any opcode"
and preserving the previous behavior. When set to a valid opcode
(<= 0xff), fault injection is only considered for commands whose opcode
matches.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Mohamed Khalfella <mkhalfella@purestorage.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions