nvme: add opcode filtering for fault injection

Browse source

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>

...

This commit is contained in:

Mohamed Khalfella 2026-08-11 16:11:52 -07:00 • committed by Keith Busch

parent 56e1c6bbe4

commit 58e7c13c8f

3 changed files with 78 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

65

Documentation/fault-injection/nvme-fault-injection.rst

View file

14

drivers/nvme/host/fault_inject.c

View file

1

drivers/nvme/host/nvme.h

View file