[SCSI] qla2xxx: Correct rport/fcport visibility-state handling during loop-resync.

Browse source

There were several issues here, one, during RSCN handling if a
follow-on RSCN occurred (within interrupt context) the DPC thread
could inadvertantly leave the fcport in a stale lost state.
Secondly, scheduled rport removal is handled exclusively by the
'parent' DPC thread, so wake up the proper thread.  Finally,
process vport loop-resync's only when the vport has in an
"active" state (ID acquired).

Signed-off-by: Seokmann Ju <seokmann.ju@qlogic.com>
Signed-off-by: Andrew Vasquez <andrew.vasquez@qlogic.com>
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>

...

This commit is contained in:

Seokmann Ju 2008-07-10 16:55:58 -07:00 • committed by James Bottomley

parent da57bf8f25

commit 5de1f70f41

3 changed files with 8 additions and 4 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

drivers/scsi/qla2xxx/qla_init.c

View file

3

drivers/scsi/qla2xxx/qla_mid.c

View file

5

drivers/scsi/qla2xxx/qla_os.c

View file