diff options
| author | Stefan Weinhuber <wein@de.ibm.com> | 2009-12-07 12:51:48 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2010-01-06 14:26:42 -0800 |
| commit | 238659281dab178c457e16b515582f0b4f4019b7 (patch) | |
| tree | 313fb8eb3facc1900219af284a35dfc5d932a1fa /lib/string_helpers.c | |
| parent | 1e856b3bc1a27e2a41b64af46296112a8aa6a7bd (diff) | |
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>
Diffstat (limited to 'lib/string_helpers.c')
0 files changed, 0 insertions, 0 deletions