qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhenzhong Duan <zhenzhong.duan@intel.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, clg@redhat.com, thuth@redhat.com,
	akrowiak@linux.ibm.com, pasic@linux.ibm.com,
	jjherne@linux.ibm.com, farman@linux.ibm.com,
	mjrosato@linux.ibm.com, borntraeger@linux.ibm.com, aik@ozlabs.ru,
	eric.auger@redhat.com, yi.l.liu@intel.com, chao.p.peng@intel.com,
	qemu-s390x@nongnu.org
Subject: [PATCH 0/3] vfio: memory leak fix and code cleanup
Date: Mon,  9 Oct 2023 10:20:45 +0800	[thread overview]
Message-ID: <20231009022048.35475-1-zhenzhong.duan@intel.com> (raw)

Hi,

This trivial patchset fixes a incremental memory leak in rare case,
and some cleanup on ap/ccw.

This patchset is based on vfio-next.

Thanks
Zhenzhong

Zhenzhong Duan (3):
  vfio/pci: Fix a potential memory leak in vfio_listener_region_add
  vfio/ap: Remove pointless apdev variable
  vfio/ccw: Remove redundant definition of TYPE_VFIO_CCW

 hw/vfio/ap.c                | 9 +++------
 hw/vfio/common.c            | 2 +-
 include/hw/s390x/vfio-ccw.h | 2 --
 3 files changed, 4 insertions(+), 9 deletions(-)

-- 
2.34.1



             reply	other threads:[~2023-10-09  2:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  2:20 Zhenzhong Duan [this message]
2023-10-09  2:20 ` [PATCH 1/3] vfio/pci: Fix a potential memory leak in vfio_listener_region_add Zhenzhong Duan
2023-10-09  2:20 ` [PATCH 2/3] vfio/ap: Remove pointless apdev variable Zhenzhong Duan
2023-10-09  6:26   ` Philippe Mathieu-Daudé
2023-10-09 14:49   ` Tony Krowiak
2023-10-09  2:20 ` [PATCH 3/3] vfio/ccw: Remove redundant definition of TYPE_VFIO_CCW Zhenzhong Duan
2023-10-09  6:26   ` Philippe Mathieu-Daudé
2023-10-09 18:58   ` Eric Farman
2023-10-09 20:53     ` Cédric Le Goater
2023-10-09  6:31 ` [PATCH 0/3] vfio: memory leak fix and code cleanup Cédric Le Goater
2023-10-09  6:54   ` Duan, Zhenzhong
2023-10-09 13:00 ` Cédric Le Goater

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=20231009022048.35475-1-zhenzhong.duan@intel.com \
    --to=zhenzhong.duan@intel.com \
    --cc=aik@ozlabs.ru \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=chao.p.peng@intel.com \
    --cc=clg@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=yi.l.liu@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).