Mohamed Khalfella 58e7c13c8f 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>

2026-08-19 07:51:23 -07:00

..

fault-injection.rst

docs: fault-injection: drop reference to md-faulty

2025-07-24 08:31:46 -06:00

index.rst

Documentation: use a source-read extension for the index link boilerplate

2026-01-23 11:59:34 -07:00

notifier-error-inject.rst

docs: notifier-error-inject: Correct test's name

2022-10-07 10:32:16 -06:00

nvme-fault-injection.rst

nvme: add opcode filtering for fault injection

2026-08-19 07:51:23 -07:00

provoke-crashes.rst

lkdtm: replace ll_rw_block with submit_bh

2023-05-31 20:26:57 +01:00