From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
James Bottomley <jbottomley@parallels.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 1/3] scsi: serialize ->rescan against ->remove
Date: Fri, 30 Jan 2015 10:46:17 +0100 [thread overview]
Message-ID: <54CB52E9.6000302@redhat.com> (raw)
In-Reply-To: <20150130010849.GA4794@ad.nay.redhat.com>
On 30/01/2015 02:08, Fam Zheng wrote:
> On Fri, 01/30 00:11, Paolo Bonzini wrote:
>>
>>
>> On 29/01/2015 00:00, Christoph Hellwig wrote:
>>> Lock the device embedded in the scsi_device to protect against
>>> concurrent calls to ->remove.
>>>
>>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>>
>> I wonder if this makes this problem: https://lkml.org/lkml/2015/1/5/9 go
>> away.
>
> A quick test says yes.
Great, we might want to revert that patch in 3.21.
Paolo
next prev parent reply other threads:[~2015-01-30 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 23:00 [PATCH 1/3] scsi: serialize ->rescan against ->remove Christoph Hellwig
2015-01-28 23:00 ` [PATCH 2/3] sd: don't grab a device references from driver methods Christoph Hellwig
2015-01-28 23:00 ` [PATCH 3/3] scsi: proper state checking and module refcount handling in scsi_device_get Christoph Hellwig
2015-01-29 14:46 ` James Bottomley
2015-01-29 20:09 ` [PATCH 1/3] scsi: serialize ->rescan against ->remove Alan Stern
2015-01-29 23:11 ` Paolo Bonzini
2015-01-30 1:08 ` Fam Zheng
2015-01-30 9:46 ` Paolo Bonzini [this message]
2015-02-02 12:59 ` Christoph Hellwig
2015-02-02 13:14 ` Paolo Bonzini
2015-02-02 13:01 Christoph Hellwig
2015-03-05 13:33 ` Christoph Hellwig
2015-03-05 13:37 ` Paolo Bonzini
2015-03-16 17:29 ` Paolo Bonzini
2015-03-05 13:36 ` Paolo Bonzini
2015-03-10 16:20 ` Hannes Reinecke
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=54CB52E9.6000302@redhat.com \
--to=pbonzini@redhat.com \
--cc=bvanassche@acm.org \
--cc=famz@redhat.com \
--cc=hch@lst.de \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.