From: Jeff Garzik <jeff@garzik.org>
To: Ed Lin <ed.lin@promise.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
"james.Bottomley" <james.Bottomley@SteelEye.com>,
promise_linux <promise_linux@promise.com>
Subject: Re: [PATCH 3/4] stex: fix reset recovery for console device
Date: Thu, 10 May 2007 17:04:12 -0400 [thread overview]
Message-ID: <464388CC.8030103@garzik.org> (raw)
In-Reply-To: <NONAMEBPke3fzk76oJD00001143@nonameb.ptu.promise.com>
Ed Lin wrote:
> After reset completed, the scsi error handler sends out TEST_UNIT_READY
> to the device. For 'normal' devices the command will be handled by firmware.
> However, because the RAID console only interfaces to scsi mid layer, the
> firmware will not process the command for it. This will make the console to
> be offlined right after reset. Add the handling in driver to fix this problem.
>
> Signed-off-by: Ed Lin <ed.lin@promise.com>
> ---
> diff --git a/drivers/scsi/stex.c b/drivers/scsi/stex.c
> index 81dd3b7..47c2ef9 100644
> --- a/drivers/scsi/stex.c
> +++ b/drivers/scsi/stex.c
> @@ -612,6 +612,13 @@ stex_queuecommand(struct scsi_cmnd *cmd,
> return 0;
> }
> break;
> + case TEST_UNIT_READY:
> + if (id == host->max_id - 1) {
> + cmd->result = DID_OK << 16 | COMMAND_COMPLETE << 8;
> + done(cmd);
> + return 0;
> + }
> + break;
Long term, it seems like a more obvious separation between the RAID
console and the firmware-handled devices would be useful, rather than
repeating the "if (id == host->max_id - 1)" for each command in question.
prev parent reply other threads:[~2007-05-10 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 4:50 [PATCH 3/4] stex: fix reset recovery for console device Ed Lin
2007-05-10 21:04 ` Jeff Garzik [this message]
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=464388CC.8030103@garzik.org \
--to=jeff@garzik.org \
--cc=ed.lin@promise.com \
--cc=james.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=promise_linux@promise.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.