All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Dan Williams <djbw@fb.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <jbottomley@parallels.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
	Chanho Min <chanho.min@lge.com>
Subject: Re: [PATCH 3/3] Make blk_cleanup_queue() wait until request_fn finished
Date: Tue, 02 Oct 2012 08:37:43 +0200	[thread overview]
Message-ID: <506A8BB7.6040007@acm.org> (raw)
In-Reply-To: <CAA9_cmcJC+xFZigKWBjXPvKY39diN0iTMTWXMSep7++YRt1Dfw@mail.gmail.com>

On 10/01/12 19:41, Dan Williams wrote:
> On Thu, Sep 27, 2012 at 9:39 AM, Bart Van Assche <bvanassche@acm.org> wrote:
 >> [ ... ]
>> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>> index 593fc71..03571a3 100644
>> --- a/drivers/scsi/scsi_lib.c
>> +++ b/drivers/scsi/scsi_lib.c
>> @@ -1517,10 +1517,6 @@ static void scsi_request_fn(struct request_queue *q)
>>          struct scsi_cmnd *cmd;
>>          struct request *req;
>>
>> -       if(!get_device(&sdev->sdev_gendev))
>> -               /* We must be tearing the block queue down already */
>> -               return;
>> -
>>          /*
>>           * To start with, we keep looping until the queue is empty, or until
>>           * the host is no longer able to accept any more requests.
>> @@ -1629,11 +1625,7 @@ out_delay:
>>          if (sdev->device_busy == 0)
>>                  blk_delay_queue(q, SCSI_QUEUE_DELAY);
>>   out:
>> -       /* must be careful here...if we trigger the ->remove() function
>> -        * we cannot be holding the q lock */
>> -       spin_unlock_irq(q->queue_lock);
>> -       put_device(&sdev->sdev_gendev);
>> -       spin_lock_irq(q->queue_lock);
>> +       ;
>
> Any reason to keep this "out:" label now that it has no effect?

Some people prefer a single-exit style for kernel code since that style 
makes it easy to add cleanup code for resources allocated inside the 
function itself. I don't have a strong opinion about this though.

Note: after I posted this patch series I noticed that patch 2/3 leaves a 
(small) race window. I'm currently testing this follow-up patch:

diff --git a/block/blk-core.c b/block/blk-core.c
index f0efe32..3991f8e 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -425,6 +425,9 @@ void blk_drain_queue(struct request_queue *q, bool 
drain_all)
                         }
                 }

+               if (!drain && blk_queue_dying(q))
+                       queue_flag_set(QUEUE_FLAG_DEAD, q);
+
                 spin_unlock_irq(q->queue_lock);

                 if (!drain)
@@ -525,10 +528,6 @@ void blk_cleanup_queue(struct request_queue *q)
         /* drain all requests queued before DEAD marking */
         blk_drain_queue(q, true);

-       spin_lock_irq(lock);
-       queue_flag_set(QUEUE_FLAG_DEAD, q);
-       spin_unlock_irq(lock);
-
         /* @q won't process any more request, flush async actions */
         del_timer_sync(&q->backing_dev_info.laptop_mode_wb_timer);
         blk_sync_queue(q);

      reply	other threads:[~2012-10-02  6:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 16:34 [PATCH 0/3 v3] blk_cleanup_queue() versus request_fn order fix Bart Van Assche
2012-09-27 16:35 ` [PATCH 1/3] block: Rename queue dead flag Bart Van Assche
2012-09-27 16:38 ` [PATCH 2/3] block: Avoid that request_fn is invoked on a dead queue Bart Van Assche
2012-09-27 16:39 ` [PATCH 3/3] Make blk_cleanup_queue() wait until request_fn finished Bart Van Assche
2012-10-01 17:41   ` Dan Williams
2012-10-02  6:37     ` Bart Van Assche [this message]

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=506A8BB7.6040007@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=chanho.min@lge.com \
    --cc=djbw@fb.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 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.