Update command result handling
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Update command result handling
Currently we're updating the request result upon completion only for BLK_PC requests. This makes it impossible for the upper layers to reliable detect the real cause for an I/O failure. By attaching the result and the sense to all requests we can update multipathing to make some more elaborate choices on how to handle I/O errors.
This also solves a potential data corruption with multipathing and persistent reservations. When queue_if_no_path is active multipath will queue any I/O failure (including those failed with RESERVATION CONFLICT) until the reservation status changes. But by then I/O might have been ongoing on the other paths, thus the delayed submission will severely corrupt your data.