From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Christie Subject: Re: [PATCH 4/4] scsi: Stop accepting SCSI requests before removing a device Date: Tue, 05 Jun 2012 16:36:09 -0500 Message-ID: <4FCE7BC9.1010504@cs.wisc.edu> References: <4FCE3D20.4000205@acm.org> <4FCE3E63.7000002@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from sabe.cs.wisc.edu ([128.105.6.20]:49059 "EHLO sabe.cs.wisc.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751879Ab2FEVgf (ORCPT ); Tue, 5 Jun 2012 17:36:35 -0400 In-Reply-To: <4FCE3E63.7000002@acm.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Bart Van Assche Cc: linux-scsi , James Bottomley , Jun'ichi Nomura , Stefan Richter , Jens Axboe , Joe Lawrence On 06/05/2012 12:14 PM, Bart Van Assche wrote: > Avoid that the code for requeueing SCSI requests triggers a > crash by making sure that that code isn't scheduled anymore > after a device has been removed. > > Also, source code inspection of __scsi_remove_device() revealed > a race condition in this function: no new SCSI requests must be > accepted for a SCSI device after device removal started. > > Signed-off-by: Bart Van Assche > Cc: Mike Christie > Cc: James Bottomley > Cc: Jens Axboe > Cc: Joe Lawrence > Cc: Jun'ichi Nomura > Cc: > --- > drivers/scsi/scsi_lib.c | 7 ++++--- > drivers/scsi/scsi_sysfs.c | 11 +++++++++-- > 2 files changed, 13 insertions(+), 5 deletions(-) > > diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c > index 082c1e5..b722a8b 100644 > --- a/drivers/scsi/scsi_lib.c > +++ b/drivers/scsi/scsi_lib.c > @@ -158,10 +158,11 @@ static void __scsi_queue_insert(struct scsi_cmnd *cmd, int reason, int unbusy) > * that are already in the queue. > */ > spin_lock_irqsave(q->queue_lock, flags); > - blk_requeue_request(q, cmd->request); > + if (!blk_queue_dead(q)) { > + blk_requeue_request(q, cmd->request); > + kblockd_schedule_work(q, &device->requeue_work); > + } If we do not requeue what eventually frees the request?