From: "Julian Calaby" <julian.calaby@gmail.com>
To: Swen Schillig <swen.schillig@freenet.de>
Cc: linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH] zfcp: Stop system after memory corruption
Date: Tue, 8 May 2007 01:56:07 +1000 [thread overview]
Message-ID: <646765f40705070856y28d958f8xe2e286ab347d63a5@mail.gmail.com> (raw)
In-Reply-To: <200705071635.04585.swen.schillig@freenet.de>
On 5/8/07, Swen Schillig <swen.schillig@freenet.de> wrote:
> From: Christof Schmitt <christof.schmitt@de.ibm.com>
[snip]
> - ZFCP_LOG_NORMAL("bug: unexpected inbound "
> - "packet on adapter %s "
> - "(reqid=0x%lx, "
> - "first_element=%d, "
> - "elements_processed=%d)\n",
> - zfcp_get_busid_by_adapter(adapter),
> - (unsigned long) buffere->addr,
> - first_element,
> - elements_processed);
> - ZFCP_LOG_NORMAL("hex dump of inbound buffer "
> - "at address %p "
> - "(buffer_index=%d, "
> - "buffere_index=%d)\n", buffer,
> - buffer_index, buffere_index);
> - ZFCP_HEX_DUMP(ZFCP_LOG_LEVEL_NORMAL,
> - (char *) buffer, SBAL_SIZE);
As a minor quibble, may I suggest that these lines belong just above
the panic introduced above? I assume that they'd be useful for
debugging should this situation occur.
If I'm completely mis-understanding the situation, please disregard this email.
Thanks,
--
Julian Calaby
Email: julian.calaby@gmail.com
(please note that I'm only subscribed to linux-scsi if replying)
next prev parent reply other threads:[~2007-05-07 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 14:35 [PATCH] zfcp: Stop system after memory corruption Swen Schillig
2007-05-07 15:56 ` Julian Calaby [this message]
2007-05-08 12:58 ` Christof Schmitt
2007-05-08 13:24 ` Julian Calaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=646765f40705070856y28d958f8xe2e286ab347d63a5@mail.gmail.com \
--to=julian.calaby@gmail.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=swen.schillig@freenet.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox