[SCSI] libfc: don't swap OX_ID and RX_ID when sending BA_RJT
authorJoe Eykholt <jeykholt@cisco.com>
Tue, 25 Aug 2009 21:04:03 +0000 (14:04 -0700)
committerJames Bottomley <James.Bottomley@suse.de>
Thu, 10 Sep 2009 17:08:03 +0000 (12:08 -0500)
commit1d490ce33ee8b93638d09e471a3bc66ae33b6606
tree67a8da5a99d3918beb5e803d49bd5cdeb56f7e37
parent2ab7e1ecb81ce35ed8e8df512e3fc6338a4c55bb
[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>
drivers/scsi/libfc/fc_exch.c