libfc: fixup command abort handling
Status from this message: Applied to 6.8/scsi-queue, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | libfc: don't schedule abort twicedrivers/ | +11 | 1 reply | |
| 2/3 | libfc: Fixup timeout error in fc_fcp_rec_error()drivers/ | +1 | 1 reply | |
| 3/3 | libfc: map FC_TIMED_OUT to DID_TIME_OUTdrivers/ | +2 | 1 reply |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Christoph Hellwig |
|---|---|
| 1/3 | R-b |
| 2/3 | R-b |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] libfc: fixup command abort handling
From: Hannes Reinecke <[email protected]>
Hi all,
when testing command timeout with the help of XDP I found that scsi_try_to_abort_cmd() would always return 'SUCCESS' for FCoE, even if no commands could be sent over the wire. Which is not only surprising, but also can lead to data corruption as commands were never aborted.
Root cause was that aborts had been sent twice, once from FC error recovery and once from SCSI EH, with the former inducing the latter to assume that the command was already aborted.
As usual, comments and reviews are welcome.
Hannes Reinecke (3):
libfc: don't schedule abort twice
libfc: Fixup timeout error in fc_fcp_rec_error()
libfc: map FC_TIMED_OUT to DID_TIME_OUT
drivers/scsi/libfc/fc_fcp.c | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-)
Signature · 1 line
2.35.3