All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>,
	ltuikov@yahoo.com, Albert Lee <albertcc@tw.ibm.com>,
	linux-ide@vger.kernel.org,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Doug Maxey <dwm@maxeymade.com>
Subject: Re: [RFC] libata new EH document
Date: Thu, 01 Sep 2005 19:01:24 -0400	[thread overview]
Message-ID: <1125615684.4946.36.camel@mulgrave> (raw)
In-Reply-To: <43178281.20203@adaptec.com>

On Thu, 2005-09-01 at 18:36 -0400, Luben Tuikov wrote:
> So are you claiming that 
>     "the error handler clears contingent allegiance conditions" ?
> 
> Please point me to the lines in the source code where it does this
> and how it does it.

That's this bit:

static void scsi_unjam_host(struct Scsi_Host *shost)
{
	unsigned long flags;
	LIST_HEAD(eh_work_q);
	LIST_HEAD(eh_done_q);

	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));

	if (!scsi_eh_get_sense(&eh_work_q, &eh_done_q))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
		if (!scsi_eh_abort_cmds(&eh_work_q, &eh_done_q))
			scsi_eh_ready_devs(shost, &eh_work_q, &eh_done_q);

James



  reply	other threads:[~2005-09-01 23:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29  6:11 [RFC] libata new EH document Tejun Heo
2005-08-29  6:13 ` Tejun Heo
2005-08-30  9:10 ` Albert Lee
2005-08-30 10:26   ` Tejun Heo
2005-08-30 14:32     ` Luben Tuikov
2005-09-01  1:17       ` Tejun Heo
2005-09-01  2:22         ` Jeff Garzik
2005-09-01  2:42           ` Tejun Heo
2005-09-01  3:33           ` Luben Tuikov
2005-09-01  3:30         ` Luben Tuikov
2005-09-01  3:44           ` Tejun Heo
2005-09-01  4:38             ` Luben Tuikov
2005-09-01  5:44               ` Tejun Heo
2005-09-01  5:54                 ` Jeff Garzik
2005-09-01 13:24                   ` James Bottomley
2005-09-01 21:40                     ` Luben Tuikov
2005-09-01 21:46                       ` Jeff Garzik
2005-09-01 22:09                         ` Luben Tuikov
2005-09-01 22:27                           ` Jeff Garzik
2005-09-01 23:17                             ` Luben Tuikov
2005-09-02  7:09                             ` Stefan Richter
2005-09-01 22:22                         ` Luben Tuikov
2005-09-01 22:31                           ` Jeff Garzik
2005-09-01 21:55                       ` James Bottomley
2005-09-01 22:07                         ` Luben Tuikov
2005-09-01 22:23                           ` James Bottomley
2005-09-01 22:36                             ` Luben Tuikov
2005-09-01 23:01                               ` James Bottomley [this message]
2005-09-01 23:03                                 ` Luben Tuikov
2005-09-01 23:27                                 ` Luben Tuikov
2005-09-01  2:22     ` Jeff Garzik
2005-08-30 14:27   ` James Bottomley
2005-09-07  8:25 ` Jeff Garzik

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=1125615684.4946.36.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=albertcc@tw.ibm.com \
    --cc=dwm@maxeymade.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ltuikov@yahoo.com \
    --cc=luben_tuikov@adaptec.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.