From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"israelr@mellanox.com" <israelr@mellanox.com>
Cc: "maxg@mellanox.com" <maxg@mellanox.com>
Subject: Re: [PATCH v2] scsi_sysfs: fix hang when removing scsi device
Date: Thu, 16 Mar 2017 15:42:44 +0000 [thread overview]
Message-ID: <1489678950.2574.7.camel@sandisk.com> (raw)
In-Reply-To: <8e4daba5-b172-2ee1-e889-93892079e839@mellanox.com>
On Thu, 2017-03-16 at 11:02 +0200, Israel Rukshin wrote:
> I tested your patches and the hang disappeared when fast_io_fail_tmo
> expired. The warning from patch 1 still exist, so we need an additional
> fix for that.
Hello Israel,
Thanks for the testing! I will leave out patch 1 for now since it is not
needed to fix the hang.
I assume that your e-mail counts as a Tested-by?
PS: please do not top-post when replying. This is considered annoying in the
Linux kernel community.
Bart.
next prev parent reply other threads:[~2017-03-16 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 16:37 [PATCH v2] scsi_sysfs: fix hang when removing scsi device Israel Rukshin
2017-03-09 19:36 ` Bart Van Assche
2017-03-12 10:26 ` Israel Rukshin
2017-03-13 18:49 ` Bart Van Assche
2017-03-13 19:23 ` James Bottomley
2017-03-13 20:33 ` Bart Van Assche
2017-03-13 21:55 ` James Bottomley
2017-03-14 2:35 ` Bart Van Assche
2017-03-14 9:44 ` Israel Rukshin
2017-03-14 14:23 ` Israel Rukshin
2017-03-15 23:27 ` Bart Van Assche
2017-03-16 9:02 ` Israel Rukshin
2017-03-16 15:42 ` Bart Van Assche [this message]
2017-03-16 15:59 ` Israel Rukshin
2017-03-16 23:00 ` Bart Van Assche
2017-03-18 0:05 ` Bart Van Assche
2017-03-18 11:17 ` Hannes Reinecke
2017-03-18 15:28 ` 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=1489678950.2574.7.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=israelr@mellanox.com \
--cc=linux-scsi@vger.kernel.org \
--cc=maxg@mellanox.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