From: "Ewan D. Milne" <emilne@redhat.com>
To: Wei Fang <fangwei1@huawei.com>
Cc: jejb@linux.vnet.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, bart.vanassche@sandisk.com,
chenzengxi@huawei.com
Subject: Re: [PATCH v3] scsi: avoid a permanent stop of the scsi device's request queue
Date: Wed, 04 Jan 2017 10:38:52 -0500 [thread overview]
Message-ID: <1483544332.15161.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1481559825.4643.2.camel@localhost.localdomain>
On Mon, 2016-12-12 at 11:23 -0500, Ewan D. Milne wrote:
> ...I have not heard back yet
> from the site that reported this problem to me on their reproducer.
Not that it matters much now, but..
The response from my original reporter is that indeed the state was
being changed from SDEV_BLOCK -> SDEV_RUNNING in scsi_sysfs_add_sdev()
so the fix is correct.
-Ewan
prev parent reply other threads:[~2017-01-04 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 2:20 [PATCH v3] scsi: avoid a permanent stop of the scsi device's request queue Wei Fang
2016-12-12 16:23 ` Ewan D. Milne
2016-12-12 16:43 ` James Bottomley
2016-12-13 1:06 ` Wei Fang
2017-01-04 15:38 ` Ewan D. Milne [this message]
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=1483544332.15161.30.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=bart.vanassche@sandisk.com \
--cc=chenzengxi@huawei.com \
--cc=fangwei1@huawei.com \
--cc=jejb@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).