All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: sekharan@us.ibm.com
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	device-mapper development <dm-devel@redhat.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/7] scsi_dh: add generic SPC-3 alua handler
Date: Thu, 15 May 2008 10:13:18 +0200	[thread overview]
Message-ID: <482BF09E.2070905@suse.de> (raw)
In-Reply-To: <1210819780.21974.264.camel@chandra-ubuntu>

Chandra Seetharaman wrote:
> I do not know the functionality of this module. So, my comments are only
> related to code.
> 
> blk_request_rq() frees up the request before it returns (in
> blk_end_sync_rq()). So, there is no need for blk_put_request().
> 
Indeed. But this opens up another question:

By the time blk_execute_rq() returns, the request is already
put back onto the queue.
That means that I shouldn't access rq->errors any more, as
the request might have been reused already.
But blk_execute_rq() returns -EIO for any error, making it
impossible to signal a proper error here.
So how do I get the contents of rq->errors safely?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2008-05-15  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 14:43 [PATCH 3/7] scsi_dh: add generic SPC-3 alua handler Hannes Reinecke
2008-05-15  2:49 ` Chandra Seetharaman
2008-05-15  8:13   ` Hannes Reinecke [this message]
2008-05-16 18:37     ` Chandra Seetharaman
2008-05-16 20:18       ` Jens Axboe
2008-05-17  0:29         ` Chandra Seetharaman
  -- strict thread matches above, loose matches on Subject: below --
2008-05-20 14:05 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=482BF09E.2070905@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sekharan@us.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.