This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH resubmit] xen-blkfront: Don't send closing notif

To: Joe Jin <joe.jin@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH resubmit] xen-blkfront: Don't send closing notification to backend in blkfront_closing()
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Thu, 14 Jul 2011 09:13:29 +0100
Cc: Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Kurt C Hackel <KURT.HACKEL@xxxxxxxxxx>, Greg Marsden <greg.marsden@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "annie.li@xxxxxxxxxx" <annie.li@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jens Axboe <jaxboe@xxxxxxxxxxxx>, "stable@xxxxxxxxxx" <stable@xxxxxxxxxx>, Daniel Stodden <Daniel.Stodden@xxxxxxxxxx>
Delivery-date: Thu, 14 Jul 2011 01:15:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E1CEB34.5090907@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <4E1CEB34.5090907@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2011-07-13 at 01:47 +0100, Joe Jin wrote:
> When we do block device attach/detach test with below steps, umount hang and 
> the
> guest unable to shutdown:
> 1. start guest with the latest kernel.
> 2. attach new block device by xm block-attach in Dom0
> 3. mount new disk in guest
> 4. execute xm block-detach to detach the block device in dom0 until timeout
> 5. try to unmount the disk in guest, umount hung. at here, any IOs to the 
>    device will hang.
> Checking the code found when 'xm block-detach' set backend device's state to
> 'XenbusStateClosing', frontend received the notification and 
> blkfront_closing()
> be called, at the moment, the disk still using by guest, so frontend refused
> to close. In the blkfront_closing(), frontend send a notification to backend
> said that the its state switched to 'Closing', when backend got the
> event, it will disconnect from real device, at here any IO request will
> be stuck, even tried to release the disk by umount.
> Per our test, below patch fix this issue.

It's worth mentioning here that the change to xbdev->state is picked up
in blkif_release() when the device is closed and the disconnect happens
at that point instead.

I'm wondering if we might not be better off deferring the disconnect on
the backend side until the frontend enters XenbusStateClosed instead of
doing it in closing.


> Signed-off-by: Joe Jin <joe.jin@xxxxxxxxxx>
> Signed-off-by: Annie Li <annie.li@xxxxxxxxxx>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> Cc: Jens Axboe <jaxboe@xxxxxxxxxxxx>
> Cc: stable@xxxxxxxxxx
> ---
>  xen-blkfront.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
> index b536a9c..f6d8ac2 100644
> --- a/drivers/block/xen-blkfront.c
> +++ b/drivers/block/xen-blkfront.c
> @@ -1088,7 +1088,7 @@ blkfront_closing(struct blkfront_info *info)
>       if (bdev->bd_openers) {
>               xenbus_dev_error(xbdev, -EBUSY,
>                                "Device in use; refusing to close");
> -             xenbus_switch_state(xbdev, XenbusStateClosing);
> +             xbdev->state = XenbusStateClosing;
>       } else {
>               xlvbd_release_gendisk(info);
>               xenbus_frontend_closed(xbdev);

Xen-devel mailing list