From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
qemu-block@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH 0/5] block/nvme: Fix a memory leak in nvme_free_queue_pair()
Date: Wed, 6 Oct 2021 18:49:26 +0200 [thread overview]
Message-ID: <20211006164931.172349-1-philmd@redhat.com> (raw)
Hi,
While searching for a memory corruption in the NVMe block driver,
Valgrind revealed one leak. It is not what I'm looking for, but
worth fixing (at least one warning removed from the huge valgrind
report).
Philippe Mathieu-Daudé (5):
block/nvme: Automatically free qemu_memalign() with QEMU_AUTO_VFREE
block/nvme: Display CQ/SQ pointer in nvme_free_queue_pair()
block/nvme: Extract nvme_free_queue() from nvme_free_queue_pair()
block/nvme: Pass BDRVNVMeState* handle to nvme_free_queue_pair()
block/nvme: Fix memory leak from nvme_init_queue()
block/nvme.c | 31 +++++++++++++++++--------------
block/trace-events | 2 +-
2 files changed, 18 insertions(+), 15 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-06 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 16:49 Philippe Mathieu-Daudé [this message]
2021-10-06 16:49 ` [PATCH 1/5] block/nvme: Automatically free qemu_memalign() with QEMU_AUTO_VFREE Philippe Mathieu-Daudé
2021-10-07 13:29 ` Stefan Hajnoczi
2021-10-06 16:49 ` [PATCH 2/5] block/nvme: Display CQ/SQ pointer in nvme_free_queue_pair() Philippe Mathieu-Daudé
2021-10-07 13:29 ` Stefan Hajnoczi
2021-10-06 16:49 ` [PATCH 3/5] block/nvme: Extract nvme_free_queue() from nvme_free_queue_pair() Philippe Mathieu-Daudé
2021-10-07 13:29 ` Stefan Hajnoczi
2021-10-06 16:49 ` [PATCH 4/5] block/nvme: Pass BDRVNVMeState* handle to nvme_free_queue_pair() Philippe Mathieu-Daudé
2021-10-07 13:30 ` Stefan Hajnoczi
2021-10-06 16:49 ` [PATCH 5/5] block/nvme: Fix memory leak from nvme_init_queue() Philippe Mathieu-Daudé
2021-10-06 16:58 ` Philippe Mathieu-Daudé
2021-10-07 13:29 ` Stefan Hajnoczi
2021-10-07 13:34 ` Philippe Mathieu-Daudé
2021-11-02 12:33 ` Kevin Wolf
2021-11-02 12:36 ` Philippe Mathieu-Daudé
2021-11-02 14:50 ` Kevin Wolf
2021-11-02 15:17 ` Philippe Mathieu-Daudé
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=20211006164931.172349-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).