From: Laurent Vivier <laurent@vivier.eu>
To: Chen Qun <kuhn.chenqun@huawei.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: lvivier@redhat.com, zhang.zhanghailiang@huawei.com,
Viktor Prutyanov <viktor.prutyanov@phystech.edu>,
Li Qiang <liq3ea@gmail.com>,
pannengyuan@huawei.com, ganqixin@huawei.com,
Euler Robot <euler.robot@huawei.com>
Subject: Re: [PATCH RESEND v2 3/7] elf2dmp/qemu_elf: Plug memleak in QEMU_Elf_init
Date: Sun, 13 Dec 2020 18:44:01 +0100 [thread overview]
Message-ID: <1973545a-9f9b-94d0-fadd-ec7c24fd33b8@vivier.eu> (raw)
In-Reply-To: <20201023061218.2080844-4-kuhn.chenqun@huawei.com>
Le 23/10/2020 à 08:12, Chen Qun a écrit :
> From: Pan Nengyuan <pannengyuan@huawei.com>
>
> Missing g_error_free in QEMU_Elf_init() error path. Fix that.
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Pan Nengyuan <pannengyuan@huawei.com>
> Reviewed-by: Viktor Prutyanov <viktor.prutyanov@phystech.edu>
> Reviewed-by: Li Qiang <liq3ea@gmail.com>
> Signed-off-by: Chen Qun <kuhn.chenqun@huawei.com>
> ---
> contrib/elf2dmp/qemu_elf.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/contrib/elf2dmp/qemu_elf.c b/contrib/elf2dmp/qemu_elf.c
> index 0db7816586..b601b6d7ba 100644
> --- a/contrib/elf2dmp/qemu_elf.c
> +++ b/contrib/elf2dmp/qemu_elf.c
> @@ -126,6 +126,7 @@ int QEMU_Elf_init(QEMU_Elf *qe, const char *filename)
> qe->gmf = g_mapped_file_new(filename, TRUE, &gerr);
> if (gerr) {
> eprintf("Failed to map ELF dump file \'%s\'\n", filename);
> + g_error_free(gerr);
> return 1;
> }
>
>
Applied to my trivial-patches branch.
Thanks,
Laurent
next prev parent reply other threads:[~2020-12-13 17:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 6:12 [PATCH RESEND v2 0/7] some memleak trivial patchs Chen Qun
2020-10-23 6:12 ` [PATCH RESEND v2 1/7] tests/migration: fix memleak in wait_command/wait_command_fd Chen Qun
2020-10-23 6:34 ` Thomas Huth
2020-10-26 9:51 ` Maxim Levitsky
2020-10-23 6:12 ` [PATCH RESEND v2 2/7] qga/channel-posix: Plug memory leak in ga_channel_write_all() Chen Qun
2020-12-14 2:04 ` Chenqun (kuhn)
2020-10-23 6:12 ` [PATCH RESEND v2 3/7] elf2dmp/qemu_elf: Plug memleak in QEMU_Elf_init Chen Qun
2020-10-23 7:22 ` Thomas Huth
2020-12-13 17:44 ` Laurent Vivier [this message]
2020-12-14 2:26 ` Chenqun (kuhn)
2020-10-23 6:12 ` [PATCH RESEND v2 4/7] elf2dmp/pdb: Plug memleak in pdb_init_from_file Chen Qun
2020-10-23 7:22 ` Thomas Huth
2020-12-13 17:44 ` Laurent Vivier
2020-10-23 6:12 ` [PATCH RESEND v2 5/7] migration/colo: Plug memleaks in colo_process_incoming_thread Chen Qun
2020-12-14 3:12 ` Chenqun (kuhn)
2020-10-23 6:12 ` [PATCH RESEND v2 6/7] blockdev: Fix a memleak in drive_backup_prepare() Chen Qun
2020-12-13 17:50 ` Laurent Vivier
2020-10-23 6:12 ` [PATCH RESEND v2 7/7] block/file-posix: fix a possible undefined behavior Chen Qun
2020-12-13 17:46 ` Laurent Vivier
2020-10-30 10:23 ` [PATCH RESEND v2 0/7] some memleak trivial patchs Chenqun (kuhn)
2020-11-04 5:49 ` Chenqun (kuhn)
2020-12-09 2:48 ` Chenqun (kuhn)
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=1973545a-9f9b-94d0-fadd-ec7c24fd33b8@vivier.eu \
--to=laurent@vivier.eu \
--cc=euler.robot@huawei.com \
--cc=ganqixin@huawei.com \
--cc=kuhn.chenqun@huawei.com \
--cc=liq3ea@gmail.com \
--cc=lvivier@redhat.com \
--cc=pannengyuan@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=viktor.prutyanov@phystech.edu \
--cc=zhang.zhanghailiang@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 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).