linux/drivers/s390
Stefan Weinhuber 22825ab769 [S390] dasd: support DIAG access for read-only devices
When a DASD device is used with the DIAG discipline, the DIAG
initialization will indicate success or error with a respective
return code. So far we have interpreted a return code of 4 as error,
but it actually means that the initialization was successful, but
the device is read-only. To allow read-only devices to be used with
DIAG we need to accept a return code of 4 as success.

Re-initialization of the DIAG access is also part of the DIAG error
recovery. If we find that the access mode of a device has been
changed from writable to read-only while the device was in use,
we print an error message.

Signed-off-by: Stefan Weinhuber <wein@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2009-12-07 12:51:34 +01:00
..
block [S390] dasd: support DIAG access for read-only devices 2009-12-07 12:51:34 +01:00
char [S390] cio: split PGID settings and status 2009-12-07 12:51:31 +01:00
cio [S390] cio: dont unregister a busy device in ccw_device_set_offline 2009-12-07 12:51:33 +01:00
crypto [S390] zcrypt: Improve some comments 2009-10-06 10:35:09 +02:00
kvm [S390] kvm: use console_initcall() to initialize s390 virtio console 2009-09-11 10:29:52 +02:00
net [S390] s/r: cmm resume fix 2009-10-29 15:05:12 +01:00
scsi [SCSI] zfcp: Flush SCSI registration work when adding unit 2009-10-22 09:38:51 +09:00
Makefile [S390] split/move machine check handler code 2009-03-26 15:24:10 +01:00