You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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>		16 years ago
..
Makefile	…
fc_disc.c	…
fc_elsct.c	…
fc_exch.c	[SCSI] libfc: don't swap OX_ID and RX_ID when sending BA_RJT	16 years ago
fc_fcp.c	…
fc_frame.c	…
fc_lport.c	…
fc_rport.c	…