From: Jeff Garzik <jgarzik@pobox.com>
To: Hannes Reinecke <hare@suse.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
linux-ide@vger.kernel.org, Jens Axboe <axboe@suse.de>,
Kurt Garloff <garloff@suse.de>
Subject: Re: [PATCH] Fix SATA ATAPI error handling
Date: Thu, 26 May 2005 23:58:00 -0400 [thread overview]
Message-ID: <42969AC8.6070904@pobox.com> (raw)
In-Reply-To: <42418B10.6090009@suse.de>
Hannes Reinecke wrote:
> +static void scsi_invoke_strategy_handler(struct Scsi_Host *shost)
> +{
> + int rtn;
> + struct list_head *lh, *lh_sf;
> + struct scsi_cmnd *scmd;
> + unsigned long flags;
> + LIST_HEAD(eh_work_q);
> + LIST_HEAD(eh_done_q);
> +
> + rtn = shost->hostt->eh_strategy_handler(shost);
> +
> + spin_lock_irqsave(shost->host_lock, flags);
> + list_splice_init(&shost->eh_cmd_q, &eh_work_q);
> + spin_unlock_irqrestore(shost->host_lock, flags);
> +
> + SCSI_LOG_ERROR_RECOVERY(1, scsi_eh_prt_fail_stats(shost, &eh_work_q));
> +
> + list_for_each_safe(lh, lh_sf, &eh_work_q) {
> + scmd = list_entry(lh, struct scsi_cmnd, eh_entry);
> +
> + if (scsi_eh_eflags_chk(scmd, SCSI_EH_CANCEL_CMD) ||
> + !SCSI_SENSE_VALID(scmd))
> + continue;
> + scmd->retries = scmd->allowed;
> + scsi_eh_finish_cmd(scmd, &eh_done_q);
> + }
> +
> + if (!list_empty(&eh_work_q))
> + if (!scsi_eh_abort_cmds(&eh_work_q, &eh_done_q))
> + scsi_eh_ready_devs(shost, &eh_work_q, &eh_done_q);
The scsi_eh_abort_cmds() call doesn't do much, since all calls to
scsi_try_to_abort_cmd() will fail due to libata's lack of EH abort handler.
The latter code will print "aborting cmd failed" for the command, and
not much else.
Jeff
next prev parent reply other threads:[~2005-05-27 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 15:28 [PATCH] Fix SATA ATAPI error handling Hannes Reinecke
2005-05-27 3:58 ` Jeff Garzik [this message]
2005-05-27 6:52 ` Hannes Reinecke
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=42969AC8.6070904@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=garloff@suse.de \
--cc=hare@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).