[SCSI] aic7xx: mitigate HOST_MSG_LOOP invalid SCB ff panic
commit5e2f22d39ec29c33bc5a3a558ac545b952aab8b7
authorJames Bottomley <James.Bottomley@HansenPartnership.com>
Tue, 12 Feb 2008 21:55:48 +0000 (12 15:55 -0600)
committerJames Bottomley <James.Bottomley@HansenPartnership.com>
Mon, 18 Feb 2008 14:57:17 +0000 (18 08:57 -0600)
tree2233a93537c41fb235ee16197e618462605f710e
parentcbccc207128e8bbdb047f6c5fc261acf207749c1
[SCSI] aic7xx: mitigate HOST_MSG_LOOP invalid SCB ff panic

The panic occurs if we get a MSGIN or MSGOUT for an unidentified SCB
(meaning we didn't identify the outstanding command it was for).  For
MSGIN this is wrong because it could be an unsolicited negotiation
MSGIN from the target.

Still panic on unsolicited MSGOUT because this would represent a
mistake in the negotiation phases.  However, we should fix this as
well.  The specs say we should go to bus free for unexpected msgin.

Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
drivers/scsi/aic7xxx/aic7xxx_core.c