mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Annie Li <annie.li@oracle.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
	<konrad.wilk@oracle.com>
Subject: Re: [PATCH 1/1] xen-blkback: stop blkback thread of every queue in xen_blkif_disconnect
Date: Fri, 18 Aug 2017 10:14:11 +0100	[thread overview]
Message-ID: <20170818091411.cl2drb5mofmo3oav@MacBook-Pro-de-Roger.local> (raw)
In-Reply-To: <1503009826-3363-1-git-send-email-annie.li@oracle.com>

On Thu, Aug 17, 2017 at 06:43:46PM -0400, Annie Li wrote:
> If there is inflight I/O in any non-last queue, blkback returns -EBUSY
> directly, and never stops thread of remaining queue and processs them. When
> removing vbd device with lots of disk I/O load, some queues with inflight
> I/O still have blkback thread running even though the corresponding vbd
> device or guest is gone.
> And this could cause some problems, for example, if the backend device type
> is file, some loop devices and blkback thread always lingers there forever
> after guest is destroyed, and this causes failure of umounting repositories
> unless rebooting the dom0. So stop all threads properly and return -EBUSY
> if any queue has inflight I/O.
>
> Signed-off-by: Annie Li <annie.li@oracle.com>
> Reviewed-by: Herbert van den Bergh <herbert.van.den.bergh@oracle.com>
> Reviewed-by: Bhavesh Davda <bhavesh.davda@oracle.com>
> Reviewed-by: Adnan Misherfi <adnan.misherfi@oracle.com>
> ---
>  drivers/block/xen-blkback/xenbus.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/block/xen-blkback/xenbus.c b/drivers/block/xen-blkback/xenbus.c
> index 792da68..2adb859 100644
> --- a/drivers/block/xen-blkback/xenbus.c
> +++ b/drivers/block/xen-blkback/xenbus.c
> @@ -244,6 +244,7 @@ static int xen_blkif_disconnect(struct xen_blkif *blkif)
>  {
>  	struct pending_req *req, *n;
>  	unsigned int j, r;
> +	bool busy = false;
>  
>  	for (r = 0; r < blkif->nr_rings; r++) {
>  		struct xen_blkif_ring *ring = &blkif->rings[r];
> @@ -261,8 +262,10 @@ static int xen_blkif_disconnect(struct xen_blkif *blkif)
>  		 * don't have any discard_io or other_io requests. So, checking
>  		 * for inflight IO is enough.
>  		 */
> -		if (atomic_read(&ring->inflight) > 0)
> -			return -EBUSY;
> +		if (atomic_read(&ring->inflight) > 0) {
> +			busy = true;
> +			continue;
> +		}

I guess I'm missing something, but I don't see how this is solving the
problem described in the description.

If the problem is that xen_blkif_disconnect returns without cleaning
all the queues, this patch keeps the current behavior, just that it
will try to remove more queues before returning, as opposed to
returning when finding the first busy queue.

Roger.

  reply	other threads:[~2017-08-18  9:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 22:43 Annie Li
2017-08-18  9:14 ` Roger Pau Monné [this message]
2017-08-18 14:29   ` [Xen-devel] " annie li
2017-08-18 17:24     ` Roger Pau Monné
2017-08-22  7:32       ` Roger Pau Monné
2017-08-23 21:20         ` Konrad Rzeszutek Wilk
2017-08-24 21:30           ` annie li

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=20170818091411.cl2drb5mofmo3oav@MacBook-Pro-de-Roger.local \
    --to=roger.pau@citrix.com \
    --cc=annie.li@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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 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®