All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <mchristi@redhat.com>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH 14/14] target: Fix handling of removed LUNs
Date: Fri, 22 Jun 2018 03:45:18 +0000	[thread overview]
Message-ID: <5B2C70CE.7020202@redhat.com> (raw)
In-Reply-To: <20180301222632.31507-15-bart.vanassche@wdc.com>

On 06/21/2018 03:58 PM, Bart Van Assche wrote:
> On Thu, 2018-06-21 at 15:32 -0500, Mike Christie wrote:
>> I am not seeing that. I saw SCF_EMULATED_TASK_SENSE was moved but not
>> SCF_SENT_CHECK_CONDITION. The latter is set a little earlier in
>> transport_send_check_condition_and_sense.
> 
> Are you sure we need to change the code that sets SCF_SENT_CHECK_CONDITION?
> It seems to me like the name of that flag is misleading. I think that flag
> is used to keep track of whether or not a response has been sent to the
> initiator. So keeping the current code for the manipulation of that flag
> should be fine.
> 

I think with your patch the behavior will be the same as before, so it
is safe.

I was more asking if in another future patch we need to set that bit for
the case where TCM_LUN_BUSY/TCM_OUT_OF_RESOURCES is passed to
transport_generic_request_failure so the behavior for that code path is
the same as when you now set cmd->scsi_status = TCM_LUN_BUSY in your patch.




  parent reply	other threads:[~2018-06-22  3:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 22:26 [PATCH 14/14] target: Fix handling of removed LUNs Bart Van Assche
2018-06-21  1:32 ` Mike Christie
2018-06-21 17:53 ` Bart Van Assche
2018-06-21 19:10 ` Mike Christie
2018-06-21 20:25 ` Bart Van Assche
2018-06-21 20:32 ` Mike Christie
2018-06-21 20:38 ` Mike Christie
2018-06-21 20:53 ` Bart Van Assche
2018-06-21 20:58 ` Bart Van Assche
2018-06-22  3:45 ` Mike Christie [this message]
2018-06-22 15:38 ` Bart Van Assche

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=5B2C70CE.7020202@redhat.com \
    --to=mchristi@redhat.com \
    --cc=target-devel@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 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.