All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michael.christie@oracle.com>
To: "yebin (H)" <yebin10@huawei.com>,
	Benjamin Block <bblock@linux.ibm.com>,
	Ye Bin <yebin@huaweicloud.com>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: fix hung_task when change host from recovery to running via sysfs
Date: Thu, 23 Mar 2023 11:12:33 -0500	[thread overview]
Message-ID: <1df01cd0-e56e-b615-9418-e3fd69819798@oracle.com> (raw)
In-Reply-To: <641A58D0.1020205@huawei.com>

On 3/21/23 8:24 PM, yebin (H) wrote:
> 
> 
> On 2023/3/21 22:22, Benjamin Block wrote:
>> On Tue, Mar 21, 2023 at 04:42:04PM +0800, Ye Bin wrote:
>>> From: Ye Bin <yebin10@huawei.com>
>>>
>>> When do follow test:
>>> Step1: echo  "recovery" > /sys/class/scsi_host/host0/state
>> Hmm, that make me wonder, what potential use-case this is for? Just
>> testing?
> Thank you for your reply.
> Actually, I'm looking for a way to temporarily stop sending IO to the driver.

Is this just for testing something or does a user/app need this
functionality for something?

We used to be able to block specific devices but we removed that.
It was useful for people like us where we need to do some low kernel
testing like testing for how upper layers handle IO hangs, but I
think it was not useful for other users so it was removed.


  parent reply	other threads:[~2023-03-23 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  8:42 [PATCH] scsi: fix hung_task when change host from recovery to running via sysfs Ye Bin
2023-03-21 14:22 ` Benjamin Block
2023-03-22  1:24   ` yebin (H)
2023-03-23 10:21     ` Benjamin Block
2023-03-23 15:57       ` Mike Christie
2023-03-23 16:12     ` Mike Christie [this message]
2023-03-24  1:41       ` yebin (H)

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=1df01cd0-e56e-b615-9418-e3fd69819798@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=bblock@linux.ibm.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=yebin10@huawei.com \
    --cc=yebin@huaweicloud.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.