[SCSI] libfc: don't create dummy (rogue) remote ports
authorJoe Eykholt <jeykholt@cisco.com>
Tue, 25 Aug 2009 21:01:18 +0000 (14:01 -0700)
committerJames Bottomley <James.Bottomley@suse.de>
Thu, 10 Sep 2009 17:07:43 +0000 (12:07 -0500)
commit9e9d0452fe12115b1c1883c0d4d2ee509079791b
tree7cf8bb38e28e562274dcd7eeb2adfdf394876d14
parent4c0f62b5679321b2e5572cf541ffb9f7b344d47c
[SCSI] libfc: don't create dummy (rogue) remote ports

Don't create a "dummy" remote port to go with fc_rport_priv.

Make the rport truly optional by allocating fc_rport_priv separately
and not requiring a dummy rport to be there if we haven't yet done
fc_remote_port_add().

The fc_rport_libfc_priv remains as a structure attached to the
rport for I/O purposes.

Be sure to hold references on rdata when the lock is dropped in
fc_rport_work().

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_disc.c
drivers/scsi/libfc/fc_rport.c
include/scsi/libfc.h