All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Liang <liangpeng10@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: zhengchuan@huawei.com, wanghao232@huawei.com,
	qemu-devel@nongnu.org, xiexiangyou@huawei.com,
	qemu-stable@nongnu.org
Subject: Re: [PATCH] vfio: Fix memory leak of hostwin
Date: Wed, 17 Nov 2021 09:43:36 +0800	[thread overview]
Message-ID: <ef504fe3-fdf7-117d-d163-8183dc52e7e9@huawei.com> (raw)
In-Reply-To: <20211116120155.109cfd0d.alex.williamson@redhat.com>

On 11/17/2021 3:01 AM, Alex Williamson wrote:
> On Tue, 16 Nov 2021 19:56:26 +0800
> Peng Liang <liangpeng10@huawei.com> wrote:
> 
>> hostwin is allocated and added to hostwin_list in vfio_host_win_add, but
>> it is only deleted from hostwin_list in vfio_host_win_del, which causes
>> a memory leak.  Also, freeing all elements in hostwin_list is missing in
>> vfio_disconnect_container.
>>
>> Fix: 2e4109de8e58 ("vfio/spapr: Create DMA window dynamically (SPAPR IOMMU v2)")
>> CC: qemu-stable@nongnu.org
>> Signed-off-by: Peng Liang <liangpeng10@huawei.com>
>> ---
>>  hw/vfio/common.c | 12 ++++++++++--
>>  1 file changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
>> index dd387b0d3959..2cce60c5fac3 100644
>> --- a/hw/vfio/common.c
>> +++ b/hw/vfio/common.c
>> @@ -546,11 +546,12 @@ static void vfio_host_win_add(VFIOContainer *container,
>>  static int vfio_host_win_del(VFIOContainer *container, hwaddr min_iova,
>>                               hwaddr max_iova)
>>  {
>> -    VFIOHostDMAWindow *hostwin;
>> +    VFIOHostDMAWindow *hostwin, *next;
>>  
>> -    QLIST_FOREACH(hostwin, &container->hostwin_list, hostwin_next) {
>> +    QLIST_FOREACH_SAFE(hostwin, &container->hostwin_list, hostwin_next, next) {
> 
> Unnecessary conversion to _SAFE variant here, we don't continue to walk
> the list after removing an object.

Ok, I'll remove it in the next version.


Thanks,
Peng

> 
>>          if (hostwin->min_iova == min_iova && hostwin->max_iova == max_iova) {
>>              QLIST_REMOVE(hostwin, hostwin_next);
>> +            g_free(hostwin);
>>              return 0;
>>          }
>>      }
>> @@ -2239,6 +2240,7 @@ static void vfio_disconnect_container(VFIOGroup *group)
>>      if (QLIST_EMPTY(&container->group_list)) {
>>          VFIOAddressSpace *space = container->space;
>>          VFIOGuestIOMMU *giommu, *tmp;
>> +        VFIOHostDMAWindow *hostwin, *next;
>>  
>>          QLIST_REMOVE(container, next);
>>  
>> @@ -2249,6 +2251,12 @@ static void vfio_disconnect_container(VFIOGroup *group)
>>              g_free(giommu);
>>          }
>>  
>> +        QLIST_FOREACH_SAFE(hostwin, &container->hostwin_list, hostwin_next,
>> +                           next) {
>> +            QLIST_REMOVE(hostwin, hostwin_next);
>> +            g_free(hostwin);
>> +        }
>> +
> 
> This usage looks good.  Thanks,
> 
> Alex
> 
>>          trace_vfio_disconnect_container(container->fd);
>>          close(container->fd);
>>          g_free(container);
> 
> .
> 



      reply	other threads:[~2021-11-17  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 11:56 [PATCH] vfio: Fix memory leak of hostwin Peng Liang
2021-11-16 19:01 ` Alex Williamson
2021-11-17  1:43   ` Peng Liang [this message]

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=ef504fe3-fdf7-117d-d163-8183dc52e7e9@huawei.com \
    --to=liangpeng10@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=wanghao232@huawei.com \
    --cc=xiexiangyou@huawei.com \
    --cc=zhengchuan@huawei.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 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.