public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James.Bottomley@hansenpartnership.com
Cc: linux-scsi@vger.kernel.org
Subject: [PATCH 3/3 v2] libsas: fix sas_queuecommand return values
Date: Sat, 16 Jul 2011 15:00:35 -0400	[thread overview]
Message-ID: <20110716190035.GA9500@infradead.org> (raw)
In-Reply-To: <20110711185045.547083012@bombadil.infradead.org>

->queuecommand must return either 0, or one of the SCSI_MLQUEUE_* return
values.  Non-transient errors are indicated by setting cmd->result before
calling ->scsi_done and returning 0.  Fix libsas to adhere to this calling
convention.  Note that the DID_ERROR for returns from the low-level driver
might not be correct for all cases, but it's the best we can do with
the current layering in libsas.  I also suspect that the pre-existing
handling of -SAS_QUEUE_FULL should really be SCSI_MLQUEUE_HOST_BUSY, but
I'll leave that for a separate change.

Signed-off-by: Christoph Hellwig <hch@lst.de>

Index: linux-2.6/drivers/scsi/libsas/sas_scsi_host.c
===================================================================
--- linux-2.6.orig/drivers/scsi/libsas/sas_scsi_host.c	2011-07-16 11:24:36.852182194 -0700
+++ linux-2.6/drivers/scsi/libsas/sas_scsi_host.c	2011-07-16 11:24:50.022110847 -0700
@@ -207,7 +207,7 @@ int sas_queuecommand(struct Scsi_Host *h
 
 	task = sas_create_task(cmd, dev, GFP_ATOMIC);
 	if (!task)
-		return -ENOMEM;
+		return SCSI_MLQUEUE_HOST_BUSY;
 
 	/* Queue up, Direct Mode or Task Collector Mode. */
 	if (sas_ha->lldd_max_execute_num < 2)
@@ -223,9 +223,10 @@ out_free_task:
 	SAS_DPRINTK("lldd_execute_task returned: %d\n", res);
 	ASSIGN_SAS_TASK(cmd, NULL);
 	sas_free_task(task);
-	if (res != -SAS_QUEUE_FULL)
-		return res;
-	cmd->result = DID_SOFT_ERROR << 16; /* retry */
+	if (res == -SAS_QUEUE_FULL)
+		cmd->result = DID_SOFT_ERROR << 16; /* retry */
+	else
+		cmd->result = DID_ERROR << 16;
 out_done:
 	cmd->scsi_done(cmd);
 	return 0;

  parent reply	other threads:[~2011-07-16 19:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 18:49 [PATCH 0/3] RFC: libsas queuecommand fixups Christoph Hellwig
2011-07-11 18:49 ` [PATCH 1/3] libsas: sas_queuecommand doesnt need host_lock Christoph Hellwig
2011-07-18 23:40   ` Dan Williams
2011-07-18 23:42     ` Jiang, Dave
2011-07-19  8:56     ` Jack Wang
2011-07-23  2:05       ` 'Christoph Hellwig'
2011-07-11 18:49 ` [PATCH 2/3] libsas: reindent sas_queuecommand Christoph Hellwig
2011-07-11 18:49 ` [PATCH 3/3] libsas: fix sas_queuecommand return values Christoph Hellwig
2011-07-12  1:16   ` Jack Wang
2011-07-16 19:00   ` Christoph Hellwig [this message]
2011-07-12 22:10 ` [PATCH 0/3] RFC: libsas queuecommand fixups ersatz splatt
2011-08-22 14:45 ` Christoph Hellwig
2011-08-23 13:57   ` James Bottomley
2011-08-24  1:16     ` ersatz splatt

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=20110716190035.GA9500@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --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