From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Wei Fang <fangwei1@huawei.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: avoid a permanent stop of the scsi device's request queue
Date: Wed, 7 Dec 2016 08:55:24 -0800 [thread overview]
Message-ID: <d5b9960c-b68c-c636-dd1d-dfd056d99e52@sandisk.com> (raw)
In-Reply-To: <9d9b3296-09d8-0f65-f52d-33fc19c4b6c2@sandisk.com>
On 12/07/2016 08:48 AM, Bart Van Assche wrote:
> It's a known bug. Some time ago I posted a patch that serializes all
> scsi_device_set_state() calls but I have not yet found it in the list
> archives. However, that patch has not yet been merged.
See also https://www.spinics.net/lists/linux-scsi/msg66966.html.
Bart.
next prev parent reply other threads:[~2016-12-07 16:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 9:12 [PATCH] scsi: avoid a permanent stop of the scsi device's request queue Wei Fang
2016-12-06 15:51 ` Bart Van Assche
2016-12-07 1:20 ` Wei Fang
2016-12-07 2:45 ` Bart Van Assche
2016-12-07 3:41 ` Wei Fang
2016-12-07 4:40 ` Bart Van Assche
2016-12-07 6:59 ` Wei Fang
2016-12-07 16:48 ` Bart Van Assche
2016-12-07 16:55 ` Bart Van Assche [this message]
2016-12-07 17:40 ` Ewan D. Milne
2016-12-07 18:16 ` James Bottomley
2016-12-07 19:24 ` Ewan D. Milne
2016-12-07 20:09 ` James Bottomley
2016-12-07 20:30 ` Ewan D. Milne
2016-12-07 23:43 ` James Bottomley
2016-12-08 2:28 ` Wei Fang
2016-12-08 2:33 ` James Bottomley
2016-12-08 3:22 ` Wei Fang
2016-12-08 6:38 ` Wei Fang
2016-12-08 14:04 ` Ewan D. Milne
2016-12-08 15:39 ` James Bottomley
2016-12-09 1:08 ` Wei Fang
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=d5b9960c-b68c-c636-dd1d-dfd056d99e52@sandisk.com \
--to=bart.vanassche@sandisk.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).