fix block timeout residue problems
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest7 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | aacraid: switch to block timeoutdrivers/ | +2 | 0 replies | |
| 2/7 | ibmvscsi: switch to block timeoutdrivers/ | +1 | 0 replies | |
| 3/7 | megaraid_sas: switch to block timeoutdrivers/ | +2 | 1 reply | |
| 4/7 | make scsi_eh_try_stu use block timeoutdrivers/ | +1 | 1 reply | |
| 5/7 | st: update to use block timeoutdrivers/ | +28 | 1 reply | |
| 6/7 | stex: switch to block timeoutdrivers/ | +1 | 0 replies | |
| 7/7 | remove timeout from struct scsi_deviceinclude/ | +0 | 0 replies |
Reviews trailers per patch
1 of 7 patches has a Reviewed-by or Acked-by.
| Patch | Kai Makisara |
|---|---|
| 1/7 | |
| 2/7 | |
| 3/7 | |
| 4/7 | |
| 5/7 | A-b |
| 6/7 | |
| 7/7 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/7] fix block timeout residue problems
It looks like there was only a partial conversion of the SCSI layer to the block timeout. The missing piece was killing timeout in struct scsi_device and leaving it with a zero value. This has already resulted in a regression:
http://bugzilla.kernel.org/show_bug.cgi?id=12120
But on closer inspection, there were lots of other dangling driver uses of the timeout value which would likewise have introduced hard to trace regressions.
This patch series eliminates the timeout variable from struct scsi_device and makes everything uniformly use the block timeout. Any wrong use of the scsi device timeout will now result in a compile failure.
It's getting late in the -rc series to push this through, but hopefully it won't delay 2.6.28 too much.
James