Christof Schmitt b03670e527 [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>		2007-05-08 11:19:50 -05:00
..
Makefile
zfcp_aux.c	[PATCH] mark struct file_operations const 5	2007-02-12 09:48:45 -08:00
zfcp_ccw.c
zfcp_dbf.c	[S390] Avoid excessive inlining.	2007-02-05 21:18:53 +01:00
zfcp_def.h
zfcp_erp.c	[SCSI] zfcp: fix initialization of FSF timer	2007-04-01 10:27:58 -05:00
zfcp_ext.h	Merge branch 'linus'	2007-02-10 13:45:43 -06:00
zfcp_fsf.c	[SCSI] zfcp: fix likely/unlikely usage	2007-03-11 11:12:36 -05:00
zfcp_fsf.h
zfcp_qdio.c	[SCSI] zfcp: Stop system after memory corruption	2007-05-08 11:19:50 -05:00
zfcp_scsi.c	[S390] Get rid of a lot of sparse warnings.	2007-02-05 21:16:47 +01:00
zfcp_sysfs_adapter.c
zfcp_sysfs_driver.c
zfcp_sysfs_port.c
zfcp_sysfs_unit.c