All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xenproject.org
Cc: linux-kernel@vger.kernel.org,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] xen/xenbus: Don't leak memory when unmapping the ring on HVM backend
Date: Mon, 10 Aug 2015 14:38:44 -0400	[thread overview]
Message-ID: <55C8EFB4.5070008@oracle.com> (raw)
In-Reply-To: <1439230238-6413-1-git-send-email-julien.grall@citrix.com>



On 08/10/2015 02:10 PM, Julien Grall wrote:
> The commit ccc9d90a9a8b5c4ad7e9708ec41f75ff9e98d61d "xenbus_client:
> Extend interface to support multi-page ring" removes the call to
> free_xenballooned_pages in xenbus_unmap_ring_vfree_hvm.
>
> This will result to not give back the pages to Linux and loose them
> forever. It only happens when the backends are running in HVM domains.
>
> Signed-off-by: Julien Grall <julien.grall@citrix.com>

Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

>
> ---
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Cc: David Vrabel <david.vrabel@citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>
>
> Appeared in Linux 4.1. HVM backend, which is always the case on ARM, will
> leak every mapped ring (i.e ~12KB per domain with 1 disk and 1 vif).
> ---
>   drivers/xen/xenbus/xenbus_client.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/xen/xenbus/xenbus_client.c b/drivers/xen/xenbus/xenbus_client.c
> index 9ad3272..e303535 100644
> --- a/drivers/xen/xenbus/xenbus_client.c
> +++ b/drivers/xen/xenbus/xenbus_client.c
> @@ -814,8 +814,10 @@ static int xenbus_unmap_ring_vfree_hvm(struct xenbus_device *dev, void *vaddr)
>   
>   	rv = xenbus_unmap_ring(dev, node->handles, node->nr_handles,
>   			       addrs);
> -	if (!rv)
> +	if (!rv) {
>   		vunmap(vaddr);
> +		free_xenballooned_pages(node->nr_handles, node->hvm.pages);
> +	}
>   	else
>   		WARN(1, "Leaking %p, size %u page(s)\n", vaddr,
>   		     node->nr_handles);


  parent reply	other threads:[~2015-08-10 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 18:10 [PATCH] xen/xenbus: Don't leak memory when unmapping the ring on HVM backend Julien Grall
2015-08-10 18:38 ` Boris Ostrovsky
2015-08-10 18:38 ` Boris Ostrovsky [this message]
2015-08-10 18:46 ` Wei Liu
2015-08-10 18:46 ` Wei Liu
2015-08-11 10:05 ` [Xen-devel] " David Vrabel
2015-08-11 10:05 ` David Vrabel
  -- strict thread matches above, loose matches on Subject: below --
2015-08-10 18:10 Julien Grall

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=55C8EFB4.5070008@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --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 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.