All of lore.kernel.org
 help / color / mirror / Atom feed
From: Asias He <asias@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] virtio-blk: Fix hot-unplug race in remove method
Date: Thu, 03 May 2012 15:38:14 +0800	[thread overview]
Message-ID: <4FA235E6.1020008@redhat.com> (raw)
In-Reply-To: <20120503052751.GE8266@redhat.com>

On 05/03/2012 01:27 PM, Michael S. Tsirkin wrote:
> On Thu, May 03, 2012 at 10:19:52AM +0800, Asias He wrote:
>> If we reset the virtio-blk device before the requests already dispatched
>> to the virtio-blk driver from the block layer are finised, we will stuck
>> in blk_cleanup_queue() and the remove will fail.
>>
>> blk_cleanup_queue() calls blk_drain_queue() to drain all requests queued
>> before DEAD marking. However it will never success if the device is
>> already stopped. We'll have q->in_flight[]>  0, so the drain will not
>> finish.
>>
>> How to reproduce the race:
>> 1. hot-plug a virtio-blk device
>> 2. keep reading/writing the device in guest
>> 3. hot-unplug while the device is busy serving I/O
>>
>> Signed-off-by: Asias He<asias@redhat.com>
>
> We used to do similar tracking in -net but dropped it all by using the
> tracking that virtio core does.  Can't blk do the same?  Isn't there
> some way to use virtqueue_detach_unused_buf for this instead?

It is much simpler to use virtqueue_detach_unused_buf. Thanks, Michael.

>> ---
>>   drivers/block/virtio_blk.c |   26 ++++++++++++++++++++++----
>>   1 file changed, 22 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
>> index 72fe55d..72b818b 100644
>> --- a/drivers/block/virtio_blk.c
>> +++ b/drivers/block/virtio_blk.c
>> @@ -46,6 +46,9 @@ struct virtio_blk
>>   	/* Ida index - used to track minor number allocations. */
>>   	int index;
>>
>> +	/* Number of pending requests dispatched to driver. */
>> +	int req_in_flight;
>> +
>>   	/* Scatterlist: can be too big for stack. */
>>   	struct scatterlist sg[/*sg_elems*/];
>>   };
>> @@ -95,6 +98,7 @@ static void blk_done(struct virtqueue *vq)
>>   		}
>>
>>   		__blk_end_request_all(vbr->req, error);
>> +		vblk->req_in_flight--;
>>   		mempool_free(vbr, vblk->pool);
>>   	}
>>   	/* In case queue is stopped waiting for more buffers. */
>> @@ -190,6 +194,7 @@ static void do_virtblk_request(struct request_queue *q)
>>
>>   	while ((req = blk_peek_request(q)) != NULL) {
>>   		BUG_ON(req->nr_phys_segments + 2>  vblk->sg_elems);
>> +		vblk->req_in_flight++;
>>
>>   		/* If this request fails, stop queue and wait for something to
>>   		   finish to restart it. */
>> @@ -443,7 +448,7 @@ static int __devinit virtblk_probe(struct virtio_device *vdev)
>>   	if (err)
>>   		goto out_free_vblk;
>>
>> -	vblk->pool = mempool_create_kmalloc_pool(1,sizeof(struct virtblk_req));
>> +	vblk->pool = mempool_create_kmalloc_pool(1, sizeof(struct virtblk_req));
>>   	if (!vblk->pool) {
>>   		err = -ENOMEM;
>>   		goto out_free_vq;
>> @@ -466,6 +471,7 @@ static int __devinit virtblk_probe(struct virtio_device *vdev)
>>
>>   	virtblk_name_format("vd", index, vblk->disk->disk_name, DISK_NAME_LEN);
>>
>> +	vblk->req_in_flight = 0;
>>   	vblk->disk->major = major;
>>   	vblk->disk->first_minor = index_to_minor(index);
>>   	vblk->disk->private_data = vblk;
>> @@ -576,22 +582,34 @@ static void __devexit virtblk_remove(struct virtio_device *vdev)
>>   {
>>   	struct virtio_blk *vblk = vdev->priv;
>>   	int index = vblk->index;
>> +	unsigned long flags;
>> +	int req_in_flight;
>>
>>   	/* Prevent config work handler from accessing the device. */
>>   	mutex_lock(&vblk->config_lock);
>>   	vblk->config_enable = false;
>>   	mutex_unlock(&vblk->config_lock);
>>
>> +	/* Abort all request on the queue. */
>> +	blk_abort_queue(vblk->disk->queue);
>> +	del_gendisk(vblk->disk);
>> +
>>   	/* Stop all the virtqueues. */
>>   	vdev->config->reset(vdev);
>> -
>> +	vdev->config->del_vqs(vdev);
>>   	flush_work(&vblk->config_work);
>>
>> -	del_gendisk(vblk->disk);
>> +	/* Wait requests dispatched to device driver to finish. */
>> +	do {
>> +		spin_lock_irqsave(&vblk->lock, flags);
>> +		req_in_flight = vblk->req_in_flight;
>> +		spin_unlock_irqrestore(&vblk->lock, flags);
>> +	} while (req_in_flight != 0);
>> +
>>   	blk_cleanup_queue(vblk->disk->queue);
>>   	put_disk(vblk->disk);
>> +
>>   	mempool_destroy(vblk->pool);
>> -	vdev->config->del_vqs(vdev);
>>   	kfree(vblk);
>>   	ida_simple_remove(&vd_index_ida, index);
>>   }
>> --
>> 1.7.10
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Asias

  reply	other threads:[~2012-05-03  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  2:19 [PATCH 1/2] virtio-blk: Fix hot-unplug race in remove method Asias He
2012-05-03  5:02 ` Sasha Levin
2012-05-03  7:36   ` Asias He
2012-05-03  5:02 ` Sasha Levin
2012-05-03  5:27 ` Michael S. Tsirkin
2012-05-03  7:38   ` Asias He [this message]
2012-05-03  7:38   ` Asias He

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=4FA235E6.1020008@redhat.com \
    --to=asias@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=stefanha@gmail.com \
    --cc=virtualization@lists.linux-foundation.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.