xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Chentao(Boby)" <boby.chen@huawei.com>, konrad.wilk@oracle.com
Cc: xen-devel@lists.xenproject.org, David Vrabel <david.vrabel@citrix.com>
Subject: Re: A memory leak problem in xen-blkback module
Date: Tue, 30 Sep 2014 17:23:13 +0200	[thread overview]
Message-ID: <542ACAE1.9080305@citrix.com> (raw)
In-Reply-To: <5416B78F.50208@citrix.com>

El 15/09/14 a les 11.55, Roger Pau Monné ha escrit:
> El 12/09/14 a les 8.58, Chentao(Boby) ha escrit:
>> Hi Konrad,
>>
>>     I find a memory leak problem in xen-blkback module of linux-3.14.4 release, and the newest 3.17-rc4 also has the same problem. The problem will occur in below condition.
>>
>>     In xen_blkbk_map function, first get_free_page from balloon or the list of blkif free pages, then map this page. If get_free_page succeed, but map failed,
>> the grant handle corresponding to this page will be assigned to BLKBACK_INVALID_HANDLE. Because map failed, it will execute xen_blkbk_unmap to retrieve resources.
>> But in xen_blkbk_unmap function, if the grant handle of a page is BLKBACK_INVALID_HANDLE, it will continue to next loop to execute unmap and put_free_pages.
>> Only executes put_free_pages, these pages will be returned to the list of blkif free pages and at last be returned to balloon.
>>
>>     Make a summary, in the condition of get_free_page succeed but map failed, the page will be leaked from balloon or the list of blkif free pages. I have a immature thought,
>> in xen_blkbk_unmap funtion, when judge the grant handle of a page is BLKBACK_INVALID_HANDLE, can we execute put_free_pages to retrieve this one page?
>>
>>     Just like below:
>>     if (pages[i]->handle == BLKBACK_INVALID_HANDLE) {
>>         put_free_pages(blkif, pages[i]->page, 1);
> 
> This is not correct, and will fail to compile AFAICT. put_free_pages 
> expects an array of pointers to page structs and you are passing a 
> pointer to a page struct.
> 
> I have the following patch, which I think solves the problem. I've 
> placed the free_pages call in xen_blkbk_map itself, but it could also 
> be done in xen_blkbk_map_unmap.
> 
> ---
> commit 879ebb502e2f72279553bb0a85cc885ec492a0c1
> Author: Roger Pau Monne <roger.pau@citrix.com>
> Date:   Mon Sep 15 11:01:40 2014 +0200
> 
>     xen-blkback: fix leak on grant map error path
>     
>     Fix leaking a page when a grant mapping has failed.
>     
>     Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>     Reported by: Tao Chen <boby.chen@huawei.com>
>     ---
>     This patch should be backported to stable branches.

Ping?

  parent reply	other threads:[~2014-09-30 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12  6:58 A memory leak problem in xen-blkback module Chentao(Boby)
2014-09-15  9:55 ` Roger Pau Monné
2014-09-15 12:54   ` Chentao(Boby)
2014-09-15 13:15     ` Roger Pau Monné
2014-09-16  1:33       ` Chentao(Boby)
2014-09-30 15:23   ` Roger Pau Monné [this message]
2014-10-01 13:46     ` 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=542ACAE1.9080305@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=boby.chen@huawei.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).