mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Joe Jin <joe.jin@oracle.com>
Cc: Daniel Stodden <Daniel.Stodden@citrix.com>,
	Jens Axboe <jaxboe@fusionio.com>,
	"annie.li@oracle.com" <annie.li@oracle.com>,
	"Jeremy Fitzhardinge" <Jeremy.Fitzhardinge@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Kurt C Hackel <KURT.HACKEL@oracle.com>,
	"Greg Marsden" <greg.marsden@oracle.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH resubmit] xen-blkfront: Don't send closing  notification to backend in blkfront_closing()
Date: Thu, 14 Jul 2011 09:13:29 +0100	[thread overview]
Message-ID: <1310631209.634.444.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <4E1CEB34.5090907@oracle.com>

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.

Ian

> 
> Signed-off-by: Joe Jin <joe.jin@oracle.com>
> Signed-off-by: Annie Li <annie.li@oracle.com>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Jens Axboe <jaxboe@fusionio.com>
> Cc: stable@kernel.org
> 
> ---
>  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);



  reply	other threads:[~2011-07-14  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13  0:47 Joe Jin
2011-07-14  8:13 ` Ian Campbell [this message]
2011-07-14  8:55   ` Joe Jin
2011-07-14  9:12     ` Ian Campbell
2011-07-15  7:58       ` Joe Jin
2011-07-19 13:21         ` [Xen-devel] " Konrad Rzeszutek Wilk

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=1310631209.634.444.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@eu.citrix.com \
    --cc=Daniel.Stodden@citrix.com \
    --cc=Jeremy.Fitzhardinge@citrix.com \
    --cc=KURT.HACKEL@oracle.com \
    --cc=annie.li@oracle.com \
    --cc=greg.marsden@oracle.com \
    --cc=jaxboe@fusionio.com \
    --cc=joe.jin@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®