diff options
| author | Stefan Weinhuber <wein@de.ibm.com> | 2009-12-07 12:51:48 +0100 |
|---|---|---|
| committer | Martin Schwidefsky <sky@mschwide.boeblingen.de.ibm.com> | 2009-12-07 12:51:34 +0100 |
| commit | 22825ab7693fd29769518a0d25ba43c01a50092a (patch) | |
| tree | b4cc2d22baafb8851efac2fed87fda4982dd8209 /drivers/s390/block/dasd_fba.c | |
| parent | 6c1e3e79430615d0472dbf9f8fed89c571e66423 (diff) | |
| download | linux-stable-22825ab7693fd29769518a0d25ba43c01a50092a.tar.gz linux-stable-22825ab7693fd29769518a0d25ba43c01a50092a.tar.bz2 linux-stable-22825ab7693fd29769518a0d25ba43c01a50092a.zip | |
[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>
Diffstat (limited to 'drivers/s390/block/dasd_fba.c')
0 files changed, 0 insertions, 0 deletions