From: Fabiano Rosas <farosas@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [PATCH 0/4] arm: Fix some memory leaks
Date: Fri, 27 Feb 2026 15:52:34 -0300 [thread overview]
Message-ID: <87ldge5899.fsf@suse.de> (raw)
In-Reply-To: <20260227135736.2280161-1-peter.maydell@linaro.org>
Peter Maydell <peter.maydell@linaro.org> writes:
> This patchset fixes a couple of minor memory leaks I found by running
> "make check" for the arm targets with the clang leak sanitizer enabled.
>
> The first two patches are necessary because there are a few leaks
> that are either not interesting to fix or which are not in our code,
> and which otherwise clutter up the logs with failure messages.
> We have a suppressions-file already, but it's in the scripts/oss-fuzz
> subdirectory, so I move it out as it's more widely useful than that,
> and add some more suppression lines to it.
>
> Patches 3 and 4 are the actual leak fixes, which are straightforward.
>
> This gets me what would be a clean run, except that there's something
> wrong with the refcounting of qio channel objects in the chardev code,
> which results in variously use-after-free, leak, or assertion failures
> when running the vhost-user tests in qos-test. I'm still looking at
> those, but in the meantime posting this series gives me something to
> point at as part of the repro instructions for those errors.
>
Looks like something I worked on in the past. It seems this fell through
the cracks:
https://lore.kernel.org/r/20250515222014.4161-1-farosas@suse.de
next prev parent reply other threads:[~2026-02-27 18:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 13:57 [PATCH 0/4] arm: Fix some memory leaks Peter Maydell
2026-02-27 13:57 ` [PATCH 1/4] scripts: Move lsan_suppressions.txt out of oss-fuzz subdir Peter Maydell
2026-02-27 15:04 ` Peter Maydell
2026-02-27 15:32 ` Yodel Eldar
2026-02-27 15:41 ` Peter Maydell
2026-02-27 13:57 ` [PATCH 2/4] scripts/lsan_suppressions.txt: Add more leaks Peter Maydell
2026-02-27 18:57 ` Fabiano Rosas
2026-02-27 19:10 ` Peter Maydell
2026-02-27 19:18 ` Fabiano Rosas
2026-02-27 13:57 ` [PATCH 3/4] hw/arm/aspeed_gpio: Don't leak string in aspeed_gpio_init() Peter Maydell
2026-02-27 22:22 ` Philippe Mathieu-Daudé
2026-02-28 6:33 ` Cédric Le Goater
2026-02-27 13:57 ` [PATCH 4/4] tests/qtest/iommu-smmuv3-test: Free QPCIDevice Peter Maydell
2026-02-27 19:13 ` Fabiano Rosas
2026-02-27 18:52 ` Fabiano Rosas [this message]
2026-02-27 19:01 ` [PATCH 0/4] arm: Fix some memory leaks Peter Maydell
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=87ldge5899.fsf@suse.de \
--to=farosas@suse.de \
--cc=alex.bennee@linaro.org \
--cc=clg@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.