diff options
| author | Daniel Wagner <[email protected]> | 2021-08-30 13:36:26 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2021-09-06 08:03:11 +0000 |
| commit | 1ba2e507f55c5b0cbde8c0fbfe0d9e39612a3e52 (patch) | |
| tree | 11246c0cbf90677d906a5d46ff8b4aee9092b387 /scripts/clang-tools/gen_compile_commands.py | |
| parent | nvmet: fixup buffer overrun in nvmet_subsys_attr_serial() (diff) | |
| download | kernel-1ba2e507f55c5b0cbde8c0fbfe0d9e39612a3e52.tar.gz kernel-1ba2e507f55c5b0cbde8c0fbfe0d9e39612a3e52.zip | |
nvme-tcp: Do not reset transport on data digest errors
The spec says
7.4.6.1 Digest Error handling
When a host detects a data digest error in a C2HData PDU, that host
shall continue processing C2HData PDUs associated with the command and
when the command processing has completed, if a successful status was
returned by the controller, the host shall fail the command with a
non-fatal transport error.
Currently the transport is reseted when a data digest error is
detected. Instead, when a digest error is detected, mark the final
status as NVME_SC_DATA_XFER_ERROR and let the upper layer handle
the error.
In order to keep track of the final result maintain a status field in
nvme_tcp_request object and use it to overwrite the completion queue
status (which might be successful even though a digest error has been
detected) when completing the request.
Signed-off-by: Daniel Wagner <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'scripts/clang-tools/gen_compile_commands.py')
0 files changed, 0 insertions, 0 deletions