RFC add new block layer error values
Get series with b4
b4 am 1124874230.10888.17.camel@maxVersions newest first
- v1 RFC Latest4 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | convert block layer drivers to blkerr error valuesdrivers/ drivers/ drivers/ +35 more | +112 | 8 replies | |
| 2/4 | convert dm to blkerr error valuesdrivers/ drivers/ drivers/ +2 more | +40 | 0 replies | |
| 3/4 | convert dm-multipath to blkerr error valuesdrivers/ | +52 | 0 replies | |
| 4/4 | convert scsi to blkerr error valuesdrivers/ drivers/ drivers/ +2 more | +49 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/4] add new block layer error values
The current -Exyz errors are not descriptive enough to allow upper layers like DM and MD to decide how to handle IO errors. In many cases all we get is a -EIO. The following patches introduce block layer error values for use with the bio_endio and end_that_request* functions (end_request keeps uptodate).
This is just as a RFC I am still testing and working on them and am hoping to get some comments. All patches were made against the scsi-misc-2.6 tree.