summaryrefslogtreecommitdiffstats
path: root/arch/s390/kernel
diff options
context:
space:
mode:
authorStefan Weinhuber <wein@de.ibm.com>2011-12-27 11:27:23 +0100
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2011-12-27 11:27:13 +0100
commit1afcfd5948ff27cdbc6d91e9f3cdbdd7f3b1e566 (patch)
treebef462a868ceca3a1af8509da68c981e17be2ced /arch/s390/kernel
parent85ac7ca5972d63d23aa5ea75c3834a33b951f89d (diff)
downloadop-kernel-dev-1afcfd5948ff27cdbc6d91e9f3cdbdd7f3b1e566.zip
op-kernel-dev-1afcfd5948ff27cdbc6d91e9f3cdbdd7f3b1e566.tar.gz
[S390] dasd: fix expiration handling for recovery requests
The 'expires' value of a ccw requests defines how long the device driver should wait for a response from the evice after the request has been submitted to the channel subsystem. After the expiration time (e.g. 30 seconds) the waiting request will be cancelled and started again. This protects the DASD devices from beeing blocked by errors that cause the answering I/O interrupt to be lost. In case of error recovery requests, this 'expires' value used to be set to 0, so in case of a lost interrupt, such a recovery request would never expire and block the device. To prevent this kind of problem, all recovery requests need to have an expires value > 0 as well. If not specified otherwise, this should be the same expires value as for the original request. Signed-off-by: Stefan Weinhuber <wein@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390/kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud