From: Jeff Garzik <jeff@garzik.org>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: santil@linux.vnet.ibm.com, rcjenn@linux.vnet.ibm.com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/5] ibmvscsi: Add eh_host_reset_handler
Date: Wed, 13 Jun 2007 18:30:21 -0400 [thread overview]
Message-ID: <46706FFD.5030704@garzik.org> (raw)
In-Reply-To: <200706132212.l5DMCQD9002964@d01av02.pok.ibm.com>
Brian King wrote:
> + spin_lock_irqsave(hostdata->host->host_lock, flags);
> + list_for_each_entry_safe(tmp_evt, pos, &hostdata->sent, list) {
> + list_del(&tmp_evt->list);
> + del_timer(&tmp_evt->timer);
> + if (tmp_evt->cmnd) {
> + tmp_evt->cmnd->result = (error_code << 16);
> + unmap_cmd_data(&tmp_evt->iu.srp.cmd,
> + tmp_evt,
> + tmp_evt->hostdata->dev);
> + if (tmp_evt->cmnd_done)
> + tmp_evt->cmnd_done(tmp_evt->cmnd);
> + } else if (tmp_evt->done)
> + tmp_evt->done(tmp_evt);
> + free_event_struct(&tmp_evt->hostdata->pool, tmp_evt);
> + }
> + spin_unlock_irqrestore(hostdata->host->host_lock, flags);
Since it's been so long since I bothered with the old-style error
handling, a dumb question:
Are you sure that you should be completing the commands in the host
reset handler? I thought EH took care of that, and your sole task in
the host reset handler was to reset everything attached to a single
scsi_host.
Jeff
next prev parent reply other threads:[~2007-06-13 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11817727312836-patch-mail.ibm.com>
2007-06-13 22:12 ` [PATCH 2/5] ibmvscsi: Enhanced error logging Brian King
2007-06-13 22:12 ` [PATCH 3/5] ibmvscsi: Add eh_host_reset_handler Brian King
2007-06-13 22:30 ` Jeff Garzik [this message]
2007-06-14 13:37 ` Brian King
2007-06-13 22:12 ` [PATCH 4/5] ibmvscsi: Misc. locking fixes Brian King
2007-06-13 22:12 ` [PATCH 5/5] ibmvscsi: Abort path fix Brian King
2007-06-13 22:30 ` [PATCH 1/5] ibmvscsi: Remove unnecessary map_sg check Jeff Garzik
2007-06-14 13:38 ` Brian King
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=46706FFD.5030704@garzik.org \
--to=jeff@garzik.org \
--cc=brking@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rcjenn@linux.vnet.ibm.com \
--cc=santil@linux.vnet.ibm.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.