Re: [PATCH] zfcp: Stop system after memory corruption

2007-05-08 Thread Julian Calaby
On 5/8/07, Christof Schmitt <[EMAIL PROTECTED]> wrote: On Tue, May 08, 2007 at 01:56:07AM +1000, Julian Calaby wrote: > >From: Christof Schmitt <[EMAIL PROTECTED]> > [snip] > >- ZFCP_LOG_NORMAL("bug: unexpected inbound " > >-

Re: [PATCH] zfcp: Stop system after memory corruption

2007-05-08 Thread Christof Schmitt
On Tue, May 08, 2007 at 01:56:07AM +1000, Julian Calaby wrote: > >From: Christof Schmitt <[EMAIL PROTECTED]> > [snip] > >- ZFCP_LOG_NORMAL("bug: unexpected inbound " > >- "packet on adapter %s " > >-

Re: [PATCH] zfcp: Stop system after memory corruption

2007-05-07 Thread Julian Calaby
On 5/8/07, Swen Schillig <[EMAIL PROTECTED]> wrote: From: Christof Schmitt <[EMAIL PROTECTED]> [snip] - ZFCP_LOG_NORMAL("bug: unexpected inbound " - "packet on adapter %s " -

[PATCH] zfcp: Stop system after memory corruption

2007-05-07 Thread Swen Schillig
From: Christof Schmitt <[EMAIL PROTECTED]> 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 contin