From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Bart Van Assche <bart.vanassche@sandisk.com>,
linux-scsi@vger.kernel.org, jthumshirn@suse.de,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] scsi: restart list search after unlock in scsi_remove_target
Date: Mon, 19 Oct 2015 09:01:31 -0700 [thread overview]
Message-ID: <1445270491.2188.23.camel@HansenPartnership.com> (raw)
In-Reply-To: <20151019155658.GA11453@lst.de>
On Mon, 2015-10-19 at 17:56 +0200, Christoph Hellwig wrote:
> On Mon, Oct 19, 2015 at 08:36:23AM -0700, Bart Van Assche wrote:
> > Thanks for looking into this. However, I think we need a motivation in the
> > patch description why this patch does not reintroduce the soft lockup
> > documented in patch "scsi_remove_target: fix softlockup regression on hot
> > remove" (commit bc3f02a795d3).
>
> Interesting. I tried to find the original report and what state
> changes would cause an endless loop here.
The original report is this one:
http://thread.gmane.org/gmane.linux.kernel/1348679
James
> Dan, do you remember any
> details about this bug report?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-10-19 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 14:35 [PATCH] scsi: restart list search after unlock in scsi_remove_target Christoph Hellwig
2015-10-19 15:36 ` Bart Van Assche
2015-10-19 15:56 ` Christoph Hellwig
2015-10-19 16:01 ` James Bottomley [this message]
2015-10-19 17:21 ` Dan Williams
2015-10-26 8:35 ` Johannes Thumshirn
2015-10-27 20:14 ` Bart Van Assche
2015-10-30 8:26 ` Johannes Thumshirn
2015-10-27 16:33 ` Johannes Thumshirn
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=1445270491.2188.23.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=bart.vanassche@sandisk.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
/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.