From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] hw/ppc/pegasos: Fix memory leak
Date: Mon, 3 Nov 2025 07:51:30 +0530 [thread overview]
Message-ID: <078c2da0-ac1e-4f07-a777-d8615a4456bd@linux.ibm.com> (raw)
In-Reply-To: <20251101165236.76E8B5972E3@zero.eik.bme.hu>
Hi Balaton,
Thanks for taking care of this ...
On 11/1/25 22:22, BALATON Zoltan wrote:
> Commit 9099b430a4 introduced an early return that caused a leak of a
> GString. Allocate it later to avoid the leak.
>
I think we also want to mention:
Reported-by: Peter Maydell <peter.maydell@linaro.org>
> Fixes: 9099b430a4 (hw/ppc/pegasos2: Change device tree generation)
> Resolves: Coverity CID 1642027
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
> hw/ppc/pegasos.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/pegasos.c b/hw/ppc/pegasos.c
> index 3a498edd16..8ce185de3e 100644
> --- a/hw/ppc/pegasos.c
> +++ b/hw/ppc/pegasos.c
> @@ -847,7 +847,7 @@ static struct {
> static void add_pci_device(PCIBus *bus, PCIDevice *d, void *opaque)
> {
> FDTInfo *fi = opaque;
> - GString *node = g_string_new(NULL);
> + GString *node;
Curious to know if there were any technical reasons for not using
g_autoptr which Peter initially suggested ?
Anyways, it fixes the leak, so
Reviewed-by: Harsh Prateek Bora <harshpb@linux.ibm.com>
> uint32_t cells[(PCI_NUM_REGIONS + 1) * 5];
> int i, j;
> const char *name = NULL;
> @@ -871,6 +871,7 @@ static void add_pci_device(PCIBus *bus, PCIDevice *d, void *opaque)
> break;
> }
> }
> + node = g_string_new(NULL);
> g_string_printf(node, "%s/%s@%x", fi->path, (name ?: pn),
> PCI_SLOT(d->devfn));
> if (PCI_FUNC(d->devfn)) {
next prev parent reply other threads:[~2025-11-03 2:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 16:52 [PATCH] hw/ppc/pegasos: Fix memory leak BALATON Zoltan
2025-11-02 11:41 ` Peter Maydell
2025-11-03 2:21 ` Harsh Prateek Bora [this message]
2025-11-03 9:39 ` Peter Maydell
2025-11-03 9:47 ` Harsh Prateek Bora
2025-11-03 12:33 ` BALATON Zoltan
2025-11-09 12:33 ` Harsh Prateek Bora
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=078c2da0-ac1e-4f07-a777-d8615a4456bd@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=balaton@eik.bme.hu \
--cc=npiggin@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).