diff options
author | Christof Schmitt <christof.schmitt@de.ibm.com> | 2007-05-07 16:35:04 +0200 |
---|---|---|
committer | James Bottomley <jejb@mulgrave.il.steeleye.com> | 2007-05-08 11:19:50 -0500 |
commit | b03670e5277224d1166cb5e4f610fc388186b065 (patch) | |
tree | a89c29683450afec0035acbabd4e6aaeadc02349 /include/asm-sparc64/svr4.h | |
parent | 2135be5f24ee6620ea6f2a594087d51b6a67ce7e (diff) |
[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>
Diffstat (limited to 'include/asm-sparc64/svr4.h')
0 files changed, 0 insertions, 0 deletions