Joe Eykholt 1d490ce33e [SCSI] libfc: don't swap OX_ID and RX_ID when sending BA_RJT ... I saw an lport debug message from the exchange manager saying: "lport 70500: Received response for out of range oxid:ffff" A trace showed this was a BA_RJT sent due to an incoming ABTS which arrived on an unknown exchange. So, the sender of the BA_RJT was in error, but in this case, both the initiator and responder were the same machine. The OX_ID and RX_ID should not have been reversed in this case. Signed-off-by: Joe Eykholt <jeykholt@cisco.com> Signed-off-by: Robert Love <robert.w.love@intel.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>		2009-09-10 12:08:03 -05:00
..
fc_disc.c	[SCSI] libfc: send GPN_ID in reaction to single-port RSCNs.	2009-09-10 12:08:03 -05:00
fc_elsct.c	[SCSI] libfc: send GPN_ID in reaction to single-port RSCNs.	2009-09-10 12:08:03 -05:00
fc_exch.c	[SCSI] libfc: don't swap OX_ID and RX_ID when sending BA_RJT	2009-09-10 12:08:03 -05:00
fc_fcp.c	[SCSI] libfc: change elsct to use FC_ID instead of rdata	2009-09-10 12:07:41 -05:00
fc_frame.c	[SCSI] libfc: A modular Fibre Channel library	2008-12-29 11:24:33 -06:00
fc_lport.c	[SCSI] libfc: fix handling of incoming Discover Address (ADISC) requests	2009-09-10 12:08:02 -05:00
fc_rport.c	[SCSI] libfc: fix handling of incoming Discover Address (ADISC) requests	2009-09-10 12:08:02 -05:00
Makefile	[SCSI] libfc: A modular Fibre Channel library	2008-12-29 11:24:33 -06:00