path: root/Documentation/fault-injection
diff options
authorChristoph Hellwig <>2020-08-18 09:11:29 +0200
committerJens Axboe <>2020-08-21 17:14:28 -0600
commit2eb81a3364eada43985efc0641490b73af78d0fa (patch)
tree2c4fd2a6ca79d75672aaded71f57c95eb6ad8470 /Documentation/fault-injection
parentc41ad98bebb8f4f0335b3c50dbb7583a6149dce4 (diff)
nvme: rename and document nvme_end_request
nvme_end_request is a bit misnamed, as it wraps around the blk_mq_complete_* API. It's semantics also are non-trivial, so give it a more descriptive name and add a comment explaining the semantics. Signed-off-by: Christoph Hellwig <> Reviewed-by: Sagi Grimberg <> Reviewed-by: Mike Snitzer <> Signed-off-by: Sagi Grimberg <> Signed-off-by: Jens Axboe <>
Diffstat (limited to 'Documentation/fault-injection')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/fault-injection/nvme-fault-injection.rst b/Documentation/fault-injection/nvme-fault-injection.rst
index cdb2e829228e..1d4427890d75 100644
--- a/Documentation/fault-injection/nvme-fault-injection.rst
+++ b/Documentation/fault-injection/nvme-fault-injection.rst
@@ -3,7 +3,7 @@ NVMe Fault Injection
Linux's fault injection framework provides a systematic way to support
error injection via debugfs in the /sys/kernel/debug directory. When
enabled, the default NVME_SC_INVALID_OPCODE with no retry will be
-injected into the nvme_end_request. Users can change the default status
+injected into the nvme_try_complete_req. Users can change the default status
code and no retry flag via the debugfs. The list of Generic Command
Status can be found in include/linux/nvme.h