aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorStefan Weinhuber <wein@de.ibm.com>2013-05-28 15:26:06 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2013-05-31 17:23:49 +0200
commit8b811bae69cf30e0a9676d7dcafb0cf16f13b3bc (patch)
treeb6a9d97a043b908fef134c4766248d1bad0059bc /arch
parentb56433cb782d1cc7e44fc46d2ce3917fa75d2236 (diff)
downloadkernel_goldelico_gta04-8b811bae69cf30e0a9676d7dcafb0cf16f13b3bc.zip
kernel_goldelico_gta04-8b811bae69cf30e0a9676d7dcafb0cf16f13b3bc.tar.gz
kernel_goldelico_gta04-8b811bae69cf30e0a9676d7dcafb0cf16f13b3bc.tar.bz2
s390/dasd: fix handling of gone paths
When a path is gone and dasd_generic_path_event is called with a PE_PATH_GONE event, we must assume that any I/O request on that subchannel is still running. This is unlike the dasd_generic_notify handler and the CIO_NO_PATH event, which implies that the subchannel has been cleared. If dasd_generic_path_event finds that the path has been the last usable path, it must not call dasd_generic_last_path_gone (which would reset the state of running requests), but just set the DASD_STOPPED_DC_WAIT bit. Signed-off-by: Stefan Weinhuber <wein@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions