]> git.ipfire.org Git - people/pmueller/ipfire-2.x.git/blobdiff - src/patches/suse-2.6.27.31/patches.arch/s390-12-04-zfcp_rport_handling_on_error_inject.patch
Revert "Move xen patchset to new version's subdir."
[people/pmueller/ipfire-2.x.git] / src / patches / suse-2.6.27.31 / patches.arch / s390-12-04-zfcp_rport_handling_on_error_inject.patch
diff --git a/src/patches/suse-2.6.27.31/patches.arch/s390-12-04-zfcp_rport_handling_on_error_inject.patch b/src/patches/suse-2.6.27.31/patches.arch/s390-12-04-zfcp_rport_handling_on_error_inject.patch
deleted file mode 100644 (file)
index e2b38a8..0000000
+++ /dev/null
@@ -1,29 +0,0 @@
-From: Gerald Schaefer <geraldsc@de.ibm.com>
-Subject: zfcp: no port recovery after ADISC request timeout
-References: bnc#487755,LTC#52565
-
-Symptom:     The remote port remains in error state even if we receive
-             a RSCN stating that the connection is re-established.
-Problem:     A flag is not reset which prevents the error recovery
-             to reopen the port.
-Solution:    Clear the flag in question before we trigger a ERP.
-
-Acked-by: John Jolly <jjolly@suse.de>
----
- drivers/s390/scsi/zfcp_fc.c |    3 ++-
- 1 file changed, 2 insertions(+), 1 deletion(-)
-
-Index: linux-sles11/drivers/s390/scsi/zfcp_fc.c
-===================================================================
---- linux-sles11.orig/drivers/s390/scsi/zfcp_fc.c
-+++ linux-sles11/drivers/s390/scsi/zfcp_fc.c
-@@ -370,7 +370,8 @@ static void zfcp_fc_adisc_handler(unsign
-       if (adisc->els.status) {
-               /* request rejected or timed out */
--              zfcp_erp_port_forced_reopen(port, 0, 63, NULL);
-+              zfcp_erp_port_forced_reopen(port, ZFCP_STATUS_COMMON_ERP_FAILED,
-+                                          63, NULL);
-               goto out;
-       }