Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 84b05445 authored by Joe Eykholt's avatar Joe Eykholt Committed by James Bottomley
Browse files

[SCSI] libfc: fix WARNING from fc_seq_start_next on closed exchanges 



We saw periodic messages like:

WARNING: at drivers/scsi/libfc/fc_exch.c:825 fc_seq_start_next+0x30/0x4b

This was due to trying to allocate a sequence in a request handler
when the exchange had been reset.

Delete the WARN_ON.

Signed-off-by: default avatarJoe Eykholt <jeykholt@cisco.com>
Signed-off-by: default avatarRobert Love <robert.w.love@intel.com>
Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
Signed-off-by: default avatarJames Bottomley <James.Bottomley@suse.de>
parent e9ba8b42

drivers/scsi/libfc/fc_exch.c

+0 −1
Original line number Diff line number Diff line
@@ -822,7 +822,6 @@ struct fc_seq *fc_seq_start_next(struct fc_seq *sp) 
	struct fc_exch *ep = fc_seq_exch(sp);



	spin_lock_bh(&ep->ex_lock);

	WARN_ON((ep->esb_stat & ESB_ST_COMPLETE) != 0);

	sp = fc_seq_start_next_locked(sp);

	spin_unlock_bh(&ep->ex_lock);