From: "Cédric Le Goater" <clg@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>, qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, marcandre.lureau@redhat.com,
kraxel@redhat.com, chao.p.peng@intel.com
Subject: Re: [PATCH v2 0/2] Misc fixes on vfio display
Date: Tue, 2 Jul 2024 18:05:59 +0200 [thread overview]
Message-ID: <700534b2-0439-4236-be7f-ac75234d57aa@redhat.com> (raw)
In-Reply-To: <20240701014809.255682-1-zhenzhong.duan@intel.com>
On 7/1/24 3:48 AM, Zhenzhong Duan wrote:
> Hi,
>
> This is trying to address an issue Cédric found.
> See https://www.mail-archive.com/qemu-devel@nongnu.org/msg1043142.html
> While looking into it, also found a potential memory leak.
>
> I'm sorry that I didn't find how to test this fix, because it looks
> a GFX card is needed. Any idea on how to test or help test are quite
> appreciated.
>
> Thanks
> Zhenzhong
>
> v2:
> - set dpy->edid_info to NULL in vfio_display_edid_init() err path (Marc-André)
> - remove a wrongly added g_free(*info) in vfio_get_dev_region_info() (Marc-André)
> - add R-B on patch2
>
>
> Zhenzhong Duan (2):
> vfio/display: Fix potential memleak of edid info
> vfio/display: Fix vfio_display_edid_init() error path
>
> hw/vfio/display.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
Applied to vfio-next.
Thanks,
C.
prev parent reply other threads:[~2024-07-02 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 1:48 [PATCH v2 0/2] Misc fixes on vfio display Zhenzhong Duan
2024-07-01 1:48 ` [PATCH v2 1/2] vfio/display: Fix potential memleak of edid info Zhenzhong Duan
2024-07-02 15:25 ` Cédric Le Goater
2024-07-02 15:31 ` Marc-André Lureau
2024-07-01 1:48 ` [PATCH v2 2/2] vfio/display: Fix vfio_display_edid_init() error path Zhenzhong Duan
2024-07-02 16:05 ` Cédric Le Goater [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=700534b2-0439-4236-be7f-ac75234d57aa@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@intel.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).