[SCSI] libfc: don't WARN_ON in lport_timeout for RESET state
It's possible and harmless to get FLOGI timeouts while in RESET state. Don't do a WARN_ON in that case. Also, split out the other WARN_ONs in fc_lport_timeout, so we can tell which one is hit by its line number. 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>
This commit is contained in:
parent
1b69bc062c
commit
22655ac222
|
@ -1237,10 +1237,13 @@ static void fc_lport_timeout(struct work_struct *work)
|
|||
|
||||
switch (lport->state) {
|
||||
case LPORT_ST_DISABLED:
|
||||
case LPORT_ST_READY:
|
||||
case LPORT_ST_RESET:
|
||||
WARN_ON(1);
|
||||
break;
|
||||
case LPORT_ST_READY:
|
||||
WARN_ON(1);
|
||||
break;
|
||||
case LPORT_ST_RESET:
|
||||
break;
|
||||
case LPORT_ST_FLOGI:
|
||||
fc_lport_enter_flogi(lport);
|
||||
break;
|
||||
|
|
Loading…
Reference in New Issue