]> git.ipfire.org Git - people/pmueller/ipfire-2.x.git/blame - src/patches/suse-2.6.27.39/patches.arch/s390-12-04-zfcp_rport_handling_on_error_inject.patch
Imported linux-2.6.27.39 suse/xen patches.
[people/pmueller/ipfire-2.x.git] / src / patches / suse-2.6.27.39 / patches.arch / s390-12-04-zfcp_rport_handling_on_error_inject.patch
CommitLineData
2cb7cef9
BS
1From: Gerald Schaefer <geraldsc@de.ibm.com>
2Subject: zfcp: no port recovery after ADISC request timeout
3References: bnc#487755,LTC#52565
4
5Symptom: The remote port remains in error state even if we receive
6 a RSCN stating that the connection is re-established.
7Problem: A flag is not reset which prevents the error recovery
8 to reopen the port.
9Solution: Clear the flag in question before we trigger a ERP.
10
11Acked-by: John Jolly <jjolly@suse.de>
12---
13 drivers/s390/scsi/zfcp_fc.c | 3 ++-
14 1 file changed, 2 insertions(+), 1 deletion(-)
15
16Index: linux-sles11/drivers/s390/scsi/zfcp_fc.c
17===================================================================
18--- linux-sles11.orig/drivers/s390/scsi/zfcp_fc.c
19+++ linux-sles11/drivers/s390/scsi/zfcp_fc.c
20@@ -370,7 +370,8 @@ static void zfcp_fc_adisc_handler(unsign
21
22 if (adisc->els.status) {
23 /* request rejected or timed out */
24- zfcp_erp_port_forced_reopen(port, 0, 63, NULL);
25+ zfcp_erp_port_forced_reopen(port, ZFCP_STATUS_COMMON_ERP_FAILED,
26+ 63, NULL);
27 goto out;
28 }
29