linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Joe Lawrence <Joe.Lawrence@stratus.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <jbottomley@parallels.com>,
	Mike Christie <michaelc@cs.wisc.edu>, Tejun Heo <tj@kernel.org>,
	Chanho Min <chanho.min@lge.com>,
	David Milburn <dmilburn@redhat.com>
Subject: Re: [PATCH v8 0/10] More device removal fixes
Date: Thu, 07 Feb 2013 11:40:29 +0100	[thread overview]
Message-ID: <5113849D.9060209@acm.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1302061727030.11804@jlaw-desktop.mno.stratus.com>

On 02/06/13 23:31, Joe Lawrence wrote:
> On Tue, 5 Feb 2013, Bart Van Assche wrote:
>> Fix a few race conditions that can be triggered by removing a device:
>> - Fix a race between starved list processing and device removal.
>> - Avoid that a SCSI LLD callback can get invoked after
>>    scsi_remove_host() finished.
>> - Speed up device removal by stopping error handling as soon as
>>    the SHOST_DEL or SHOST_DEL_RECOVERY state has been reached.
>> - Save and restore the host_scribble field during error handling
>>
>> These patches have been tested on top of kernel v3.8-rc6 and are also
>> available here: http://github.com/bvanassche/linux/tree/device-removal-fixes.
>
> Hi Bart,
>
> I gave your patchset a spin on our ftServer, which supports hotplug of PCI
> devices.  Before attempting a surprise HW removal of an LSI Fusion SAS-2
> SCSI controller, I issued an orderly removal through our hotplug driver.
> The device removal appeared to hang (this does not occur with vanilla
> 3.8.0-rc6).

Hello Joe,

Thanks for running this test. I have had a quick look at the mpt2sas 
_scsih_remove() implementation but I have not yet had the time to 
analyze that function entirely. My proposal is to defer further analysis 
of the interaction between the two patches that make scsi_remove_host() 
wait and the mpt2sas driver until a later time. It would be appreciated 
if you could run the following test:
* Revert the two patches that make scsi_remove_host() wait (these
   two patches should revert cleanly).
* Repeat your device removal test.
If that test runs fine, I will retest and repost this patch series 
without the two patches that make scsi_remove_host() wait.

Thanks,

Bart.


  reply	other threads:[~2013-02-07 10:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 12:44 [PATCH v8 0/10] More device removal fixes Bart Van Assche
2013-02-05 12:45 ` [PATCH v8 01/10] Fix race between starved list processing and device removal Bart Van Assche
2013-02-05 12:46 ` [PATCH v8 02/10] Remove get_device() / put_device() pair from scsi_request_fn() Bart Van Assche
2013-02-05 12:47 ` [PATCH v8 03/10] Introduce scsi_device_being_removed() Bart Van Assche
2013-02-05 12:47 ` [PATCH v8 04/10] Remove offline devices when removing a host Bart Van Assche
2013-02-05 12:48 ` [PATCH v8 05/10] Disallow changing the device state via sysfs into "deleted" Bart Van Assche
2013-02-05 12:49 ` [PATCH v8 06/10] Avoid saving/restoring interrupt state inside scsi_remove_host() Bart Van Assche
2013-02-05 12:49 ` [PATCH v8 07/10] Make scsi_remove_host() wait for device removal Bart Van Assche
2013-02-05 12:50 ` [PATCH v8 08/10] Make scsi_remove_host() wait until error handling finished Bart Van Assche
2013-02-05 12:51 ` [PATCH v8 09/10] Avoid that scsi_device_set_state() triggers a race Bart Van Assche
2013-02-05 12:51 ` [PATCH v8 10/10] Save and restore host_scribble during error handling Bart Van Assche
2013-02-06 22:31 ` [PATCH v8 0/10] More device removal fixes Joe Lawrence
2013-02-07 10:40   ` Bart Van Assche [this message]
2013-02-07 11:33   ` Bart Van Assche
2013-02-08 23:29     ` Joe Lawrence
2013-02-09  9:28       ` Bart Van Assche
2013-02-11 20:36         ` 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=5113849D.9060209@acm.org \
    --to=bvanassche@acm.org \
    --cc=Joe.Lawrence@stratus.com \
    --cc=chanho.min@lge.com \
    --cc=dmilburn@redhat.com \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=tj@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 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).