public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] set error value when failing block pc commands in prep_fn
Date: Sat, 10 Sep 2005 14:57:05 -0500	[thread overview]
Message-ID: <1126382225.4813.63.camel@mulgrave> (raw)
In-Reply-To: <1126378749.2696.4.camel@max>

On Sat, 2005-09-10 at 13:59 -0500, Mike Christie wrote:
> This patch is updated against scsi-rc-fixes which has
> Alan's patch that fixes the places where we did not set
> a error value in the request_fn.
> 
> But when we kill a block pc request in the prep function
> the  errors value is still not getting set. And if scsi_init_io
> returned BLKPREP_DEFER we missed the blk_plug_device code so
> this patch just has it go to the defer label in that case.
> 
> Patch was made against scsi-rc-fixes.

Is there a reason we shouldn't be setting the error in all cases?  I
certainly can't think of one, in which case just set it globally.
There's also a return BLKPREP_DEFER on line 1191:

	if(unlikely(specials_only) && !(req->flags & REQ_SPECIAL)) {
		if(specials_only == SDEV_QUIESCE ||
				specials_only == SDEV_BLOCK)
			return BLKPREP_DEFER;

That needs to become a goto defer; for the same reasons as outlined
above.

James




  reply	other threads:[~2005-09-10 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10 18:59 [PATCH] set error value when failing block pc commands in prep_fn Mike Christie
2005-09-10 19:57 ` James Bottomley [this message]
2005-09-10 21:45   ` Mike Christie

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=1126382225.4813.63.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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