[SCSI] zfcp: Stop system after memory corruption
authorChristof Schmitt <christof.schmitt@de.ibm.com>
Mon, 7 May 2007 14:35:04 +0000 (16:35 +0200)
committerJames Bottomley <jejb@mulgrave.il.steeleye.com>
Tue, 8 May 2007 16:19:50 +0000 (11:19 -0500)
commitb03670e5277224d1166cb5e4f610fc388186b065
treea89c29683450afec0035acbabd4e6aaeadc02349
parent2135be5f24ee6620ea6f2a594087d51b6a67ce7e
[SCSI] zfcp: Stop system after memory corruption

For each request that is sent to the FCP adapter, zfcp allocates
memory. Status information and data that is being read from the
device is written to this memory by the hardware. After that,
the hardware signals this via the response queue and zfcp
continues processing.

Now, if zfcp detects that there is a signal for an incoming
response from the hardware, but there is no outstanding request
for that request id, then some memory that can be in use anywhere
in the system has just been overwritten. This should never happen,
but if it does, stop the system with a panic.

Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com>
Signed-off-by: Swen Schillig <swen@vnet.ibm.com>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
drivers/s390/scsi/zfcp_qdio.c