From: Stuart Hayes <stuart.w.hayes@gmail.com>
To: "James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Konstantin Khorenko <khorenko@virtuozzo.com>,
devel@openvz.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] scsi/eh: fix hang adding ehandler wakeups after decrementing host_busy
Date: Wed, 8 Nov 2017 23:38:29 -0600 [thread overview]
Message-ID: <ae6cce43-108a-aec8-2023-20f04c8506e5@gmail.com> (raw)
Are there any issues with this patch (https://patchwork.kernel.org/patch/9938919/) that Pavel Tikhomirov submitted back in September? I am willing to help if there's anything I can do to help get it accepted.
The failing case I'm working on involves lots of servers with disk read/write activity with periodic INQUIRY commands that aren't supported by the target device, so the error handler gets invoked periodically, and some of the systems will hang after a day or two.
Thanks
Stuart
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
next reply other threads:[~2017-11-09 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 5:38 Stuart Hayes [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-05 12:54 [PATCH] scsi/eh: fix hang adding ehandler wakeups after decrementing host_busy Pavel Tikhomirov
2017-10-04 7:18 ` Pavel Tikhomirov
2017-10-20 7:48 ` Pavel Tikhomirov
2017-11-09 14:54 ` Pavel Tikhomirov
2017-11-21 6:10 ` Stuart Hayes
2017-11-21 8:09 ` Pavel Tikhomirov
2017-11-22 0:49 ` Stuart Hayes
2017-11-22 7:01 ` Pavel Tikhomirov
2017-11-21 8:39 ` Pavel Tikhomirov
2017-11-21 16:53 ` 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=ae6cce43-108a-aec8-2023-20f04c8506e5@gmail.com \
--to=stuart.w.hayes@gmail.com \
--cc=devel@openvz.org \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=khorenko@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ptikhomirov@virtuozzo.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).