From: Cornelia Huck <cohuck@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: Tony Krowiak <akrowiak@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
Pierre Morel <pmorel@linux.ibm.com>,
Pan Nengyuan <pannengyuan@huawei.com>,
Qemu Developers <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Euler Robot <euler.robot@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Chen Qun <kuhn.chenqun@huawei.com>
Subject: Re: [PATCH 02/12] hw/vfio/ap: Plug memleak in vfio_ap_get_group()
Date: Wed, 26 Aug 2020 13:41:18 +0200 [thread overview]
Message-ID: <20200826134118.07fdec61.cohuck@redhat.com> (raw)
In-Reply-To: <CAKXe6S+MV3fyCoyDbDV01CbuGoR8JO3e1=VAh4OFP5bKUVMXkA@mail.gmail.com>
On Wed, 26 Aug 2020 19:03:37 +0800
Li Qiang <liq3ea@gmail.com> wrote:
> Pan Nengyuan <pannengyuan@huawei.com> 于2020年8月14日周五 下午6:29写道：
> >
> > Missing g_error_free() in vfio_ap_get_group() error path. Fix that.
> >
> > Reported-by: Euler Robot <euler.robot@huawei.com>
> > Signed-off-by: Pan Nengyuan <pannengyuan@huawei.com>
>
> Reviewed-by: Li Qiang <liq3ea@gmail.com>
>
> I see Cornelia Huck has merged this in his tree.
s/his/her/ :)
> Don't know whether this series will go separate maintainer's tree or
> as go only one maintainer's tree(maybe Paolo's misc tree?).
Whatever works best, but I still plan to send a pull req this week to
flush out my queue.
next prev parent reply other threads:[~2020-08-26 11:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 16:02 [PATCH 00/12] fix some error memleaks Pan Nengyuan
2020-08-14 16:02 ` [PATCH 01/12] qga/channel-posix: Plug memory leak in ga_channel_write_all() Pan Nengyuan
2020-08-26 11:57 ` Li Qiang
2020-08-14 16:02 ` [PATCH 02/12] hw/vfio/ap: Plug memleak in vfio_ap_get_group() Pan Nengyuan
2020-08-14 9:46 ` Pierre Morel
2020-08-17 16:11 ` Cornelia Huck
2020-08-26 11:03 ` Li Qiang
2020-08-26 11:41 ` Cornelia Huck [this message]
2020-08-26 11:53 ` Li Qiang
2020-08-14 16:02 ` [PATCH 03/12] elf2dmp/qemu_elf: Plug memleak in QEMU_Elf_init Pan Nengyuan
2020-08-23 18:12 ` Viktor Prutyanov
2020-08-26 10:56 ` Li Qiang
2020-08-14 16:02 ` [PATCH 04/12] elf2dmp/pdb: Plug memleak in pdb_init_from_file Pan Nengyuan
2020-08-23 18:17 ` Viktor Prutyanov
2020-08-26 10:54 ` Li Qiang
2020-08-14 16:02 ` [PATCH 05/12] target/i386/sev: Plug memleak in sev_read_file_base64 Pan Nengyuan
2020-08-26 10:53 ` Li Qiang
2020-08-14 16:02 ` [PATCH 06/12] ui/gtk-gl-area: Plug memleak in gd_gl_area_create_context() Pan Nengyuan
2020-08-26 12:20 ` Li Qiang
2020-08-27 7:06 ` Pan Nengyuan
2020-08-27 11:08 ` Li Qiang
2020-08-14 16:02 ` [PATCH 07/12] target/i386/cpu: Fix memleak in x86_cpu_class_check_missing_features Pan Nengyuan
2020-08-26 12:25 ` Li Qiang
2020-08-14 16:02 ` [PATCH 08/12] migration/colo: Plug memleaks in colo_process_incoming_thread Pan Nengyuan
2020-08-26 12:37 ` Li Qiang
2020-08-27 3:06 ` Pan Nengyuan
2020-08-14 16:02 ` [PATCH 09/12] blockdev: Fix a memleak in drive_backup_prepare() Pan Nengyuan
2020-08-17 9:41 ` Kevin Wolf
2020-08-26 10:45 ` Li Qiang
2020-08-14 16:02 ` [PATCH 10/12] block/file-posix: fix a possible undefined behavior Pan Nengyuan
2020-08-17 8:57 ` Stefano Garzarella
2020-08-17 9:38 ` Kevin Wolf
2020-08-26 10:40 ` Li Qiang
2020-08-14 16:02 ` [PATCH 11/12] vnc-auth-sasl: Plug memleak in vnc_socket_ip_addr_string Pan Nengyuan
2020-08-26 10:37 ` Li Qiang
2020-08-14 16:02 ` [PATCH 12/12] test-util-sockets: Fix a memleak in test_socket_unix_abstract_good Pan Nengyuan
2020-08-14 14:50 ` Li Qiang
2020-08-15 3:10 ` Pan Nengyuan
2020-08-26 6:32 ` [PATCH 00/12] fix some error memleaks Pan Nengyuan
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=20200826134118.07fdec61.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=euler.robot@huawei.com \
--cc=kuhn.chenqun@huawei.com \
--cc=liq3ea@gmail.com \
--cc=pannengyuan@huawei.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--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).