qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Dong <opensource.dxs@aliyun.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: zhongguocheng@huawei.com, agraf@suse.de,
	zhugh.fnst@cn.fujitsu.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Fix memory leak on error
Date: Fri, 27 Nov 2015 14:31:35 +0800	[thread overview]
Message-ID: <5657F8C7.3060503@aliyun.com> (raw)
In-Reply-To: <87lh9l3ppu.fsf@blackfin.pond.sub.org>



On 2015/11/26 20:33, Markus Armbruster wrote:
> Stefano Dong (董兴水) <opensource.dxs@aliyun.com> writes:
> 
>> hw/ppc/spapr.c: Fix memory leak on error, it was introduced in bc09e0611
>> hw/acpi/memory_hotplug.c: Fix memory leak on error, it was introduced in 34f2af3d
>>
>> Signed-off-by: Stefano Dong (董兴水) <opensource.dxs@aliyun.com>
>> ---
>>  hw/acpi/memory_hotplug.c | 1 +
>>  hw/ppc/spapr.c           | 1 +
>>  2 files changed, 2 insertions(+)
>>
>> diff --git a/hw/acpi/memory_hotplug.c b/hw/acpi/memory_hotplug.c
>> index ce428df..e4b9a01 100644
>> --- a/hw/acpi/memory_hotplug.c
>> +++ b/hw/acpi/memory_hotplug.c
>> @@ -155,6 +155,7 @@ static void acpi_memory_hotplug_write(void *opaque, hwaddr addr, uint64_t data,
>>                  qapi_event_send_mem_unplug_error(dev->id,
>>                                                   error_get_pretty(local_err),
>>                                                   &error_abort);
>> +                error_free(local_err);
>>                  break;
>>              }
>>              trace_mhp_acpi_pc_dimm_deleted(mem_st->selector);
>> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
>> index 030ee35..3bb8bcd 100644
>> --- a/hw/ppc/spapr.c
>> +++ b/hw/ppc/spapr.c
>> @@ -125,6 +125,7 @@ static XICSState *xics_system_init(MachineState *machine,
>>              error_report("kernel_irqchip requested but unavailable: %s",
>>                           error_get_pretty(err));
>>          }
>> +        error_free(err);
>>      }
>>  
>>      if (!icp) {
> 
> Two independent instances of the same kind of bug (failure to free an
> Error after handling it).  Collecting multiple fixes of the same kind in
> one patch can be fine.  Note, however, that the combined patch spans
> separately maintained areas of the code:
> 
>     $ scripts/get_maintainer.pl -f hw/acpi/memory_hotplug.c 
>     "Michael S. Tsirkin" <mst@redhat.com> (supporter:ACPI/SMBIOS)
>     Igor Mammedov <imammedo@redhat.com> (supporter:ACPI/SMBIOS)
>     $ scripts/get_maintainer.pl -f hw/ppc/spapr.c 
>     David Gibson <david@gibson.dropbear.id.au> (supporter:sPAPR (pseries))
>     Alexander Graf <agraf@suse.de> (supporter:sPAPR (pseries))
>     Eduardo Habkost <ehabkost@redhat.com> (maintainer:NUMA)
>     qemu-ppc@nongnu.org (open list:sPAPR (pseries))
> 
> If the combined patch is trivial, cc: qemu-trivial@nongnu.org.  I figure
> this one could qualify.
> 
> If it isn't, split it up along mainenance boundaries, and cc: the
> maintainer(s) for each part.
> 
> When you fix something with serious impact, the commit message should
> give a clue when it was broken.  For minor bugs like these, it's still
> nice to do.  The acpi_memory_hotplug_write() leak was introduced in
> bc09e06 (v2.4.0), and the xics_system_init() leak in commit 34f2af3
> (v2.3.0).  Thanks for fixing the mess I made there, by the way.
> 
> Since this is a straightforward bug fix, proposing it for inclusion into
> 2.5 makes sense.  You can do that by putting [PATCH for-2.5] into the
> subject.

Thank you Markus! Thanks for teaching me a lot! You are so kind and friendly!

> 

  reply	other threads:[~2015-11-27  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 12:00 [Qemu-devel] [PATCH] Fix memory leak on error Stefano Dong (董兴水)
2015-11-26 12:33 ` Markus Armbruster
2015-11-27  6:31   ` Stefano Dong [this message]
2015-11-27 10:02     ` Markus Armbruster
2015-11-26 14:17 ` Igor Mammedov

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=5657F8C7.3060503@aliyun.com \
    --to=opensource.dxs@aliyun.com \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhongguocheng@huawei.com \
    --cc=zhugh.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).