diff options
| author | Damien Le Moal <[email protected]> | 2023-05-11 03:13:36 +0200 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2023-05-22 17:05:18 -0400 |
| commit | dffc480d2df1772d6092f46f2b4c5e0de941bd47 (patch) | |
| tree | f8f1b394ecfd042faab847436de6fba52ea1e123 /lib/test_fortify/write_overflow-strlcpy-src.c | |
| parent | 6c913257226a25879bfd6226e0ee265e98904ce6 (diff) | |
scsi: block: Introduce BLK_STS_DURATION_LIMIT
Introduce the new block I/O status BLK_STS_DURATION_LIMIT for LLDDs to
report command that failed due to a command duration limit being
exceeded. This new status is mapped to the ETIME error code to allow users
to differentiate "soft" duration limit failures from other more serious
hardware related errors.
If we compare BLK_STS_DURATION_LIMIT with BLK_STS_TIMEOUT:
-BLK_STS_DURATION_LIMIT means that the drive gave a reply indicating that
the command duration limit was exceeded before the command could be
completed. This I/O status is mapped to ETIME for user space.
-BLK_STS_TIMEOUT means that the drive never gave a reply at all.
This I/O status is mapped to ETIMEDOUT for user space.
Signed-off-by: Damien Le Moal <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Co-developed-by: Niklas Cassel <[email protected]>
Signed-off-by: Niklas Cassel <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions