public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/4] dpt_i2o: use midlayer tcq implementation
Date: Fri, 15 Nov 2019 11:29:28 +0100	[thread overview]
Message-ID: <815c5bf3-2fe3-4681-4083-710f10ea9dde@suse.de> (raw)
In-Reply-To: <20191115084857.GA24954@lst.de>

On 11/15/19 9:48 AM, Christoph Hellwig wrote:
> On Fri, Nov 15, 2019 at 09:05:52AM +0100, Hannes Reinecke wrote:
> static bool fail_posted_scbs_iter(struct request *rq, void *data, bool reserved)
>>  {
>> +	struct scsi_cmnd *cmd = blk_mq_rq_to_pdu(rq);
>>  
>> +	cmd->result = (DID_OK << 16) | SAM_STAT_TASK_SET_FULL;
> 
> Not new in this patch, but SAM_STAT_TASK_SET_FULL seems like an odd
> error code for bouncing all commands to the mid layer after an reset.
> 
Was'ne me. Personally I would go with DID_ABORTED here,
but who am I to judge ...

>> +	cmd->scsi_done(cmd);
>> +
>> +	return true;
>> +}
>> +
>> +static void adpt_fail_posted_scbs(adpt_hba* pHba)
>> +{
>> +	blk_mq_tagset_busy_iter(&pHba->host->tag_set,
>> +				fail_posted_scbs_iter, NULL);
> 
> Should this be a scsi layer helper?  In the future it also sounds
> like we migh want to move something like this to be called from
> common code, as letting the other command posted to the hardware
> just time out after a host reset is rather silly.
> 
Sure, for the common helper.

Moving it to the common layer is probably not going to work, as some
HBAs will complete commands internally during host reset (and hence
triggering a completion), while others don't (or can't, like aacraid).

So not sure about that one.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      Teamlead Storage & Networking
hare@suse.de			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 247165 (AG München), GF: Felix Imendörffer

  reply	other threads:[~2019-11-15 10:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  8:05 [PATCHv2 0/4] scsi: remove legacy cmd_list implementation Hannes Reinecke
2019-11-15  8:05 ` [PATCH 1/4] dpt_i2o: use midlayer tcq implementation Hannes Reinecke
2019-11-15  8:48   ` Christoph Hellwig
2019-11-15 10:29     ` Hannes Reinecke [this message]
2019-11-15  8:05 ` [PATCH 2/4] dpt_i2o: make adpt_i2o_to_scsi() a void function Hannes Reinecke
2019-11-15  8:51   ` Christoph Hellwig
2019-11-15  9:24     ` Hannes Reinecke
2019-11-15  8:05 ` [PATCH 3/4] aacraid: use blk_mq_rq_busy_iter() for traversing outstanding commands Hannes Reinecke
2019-11-15  9:06   ` Christoph Hellwig
2019-11-15  8:05 ` [PATCH 4/4] scsi: Remove cmd_list functionality Hannes Reinecke
  -- strict thread matches above, loose matches on Subject: below --
2019-11-01 11:18 [PATCH 0/4] scsi: remove legacy cmd_list implementation Hannes Reinecke
2019-11-01 11:18 ` [PATCH 1/4] dpt_i2o: use midlayer tcq implementation 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=815c5bf3-2fe3-4681-4083-710f10ea9dde@suse.de \
    --to=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox