From: Stefan Weinhuber Date: Mon, 7 Dec 2009 11:51:48 +0000 (+0100) Subject: [S390] dasd: support DIAG access for read-only devices X-Git-Tag: v2.6.33-rc1~349^2~37 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=22825ab7693fd29769518a0d25ba43c01a50092a;p=pandora-kernel.git [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 Signed-off-by: Martin Schwidefsky --- Reading git-diff-tree failed