From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Keith Busch <kbusch@kernel.org>, Klaus Jensen <its@irrelevant.dk>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>
Subject: [PATCH 0/2] hw/nvme: coverity fixes
Date: Tue, 11 Apr 2023 21:04:46 +0200 [thread overview]
Message-ID: <20230411190448.64863-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Fix two issues reported by Coverity (CID 1507979 and 1508281).
Klaus Jensen (2):
hw/nvme: fix memory leak in fdp ruhid parsing
hw/nvme: fix memory leak in nvme_dsm
hw/nvme/ctrl.c | 3 +++
hw/nvme/ns.c | 3 ++-
2 files changed, 5 insertions(+), 1 deletion(-)
--
2.39.2
next reply other threads:[~2023-04-11 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 19:04 Klaus Jensen [this message]
2023-04-11 19:04 ` [PATCH 1/2] hw/nvme: fix memory leak in fdp ruhid parsing Klaus Jensen
2023-04-12 9:47 ` Philippe Mathieu-Daudé
2023-04-11 19:04 ` [PATCH 2/2] hw/nvme: fix memory leak in nvme_dsm Klaus Jensen
2023-04-12 9:54 ` Philippe Mathieu-Daudé
2023-04-12 10:02 ` Klaus Jensen
2023-04-12 9:40 ` [PATCH 0/2] hw/nvme: coverity fixes Klaus Jensen
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=20230411190448.64863-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).