Stefan Weinhuber 238659281d S390: dasd: support DIAG access for read-only devices ...

commit 22825ab7693fd29769518a0d25ba43c01a50092a upstream.

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>
Cc: Stephen Powell <zlinuxman@wowway.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

2010-01-06 14:26:42 -08:00

..

block

S390: dasd: support DIAG access for read-only devices

2010-01-06 14:26:42 -08:00

char

[S390] improve suspend/resume error messages

2009-07-07 16:37:53 +02:00

cio

[S390] cio: fix double free after failed device initialization

2009-08-23 18:10:00 +02:00

crypto

[S390] zcrypt: fix scheduling of hrtimer ap_poll_timer

2009-07-24 12:41:02 +02:00

kvm

virtio: find_vqs/del_vqs virtio operations

2009-06-12 22:16:36 +09:30

net

[S390] driver_data access

2009-06-22 12:08:23 +02:00

scsi

[SCSI] zfcp: Fix tracing of request id for abort requests

2009-07-30 08:49:59 -05:00

Makefile

[S390] split/move machine check handler code

2009-03-26 15:24:10 +01:00