From: Fabiano Rosas <farosas@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [PATCH 2/4] scripts/lsan_suppressions.txt: Add more leaks
Date: Fri, 27 Feb 2026 16:18:27 -0300 [thread overview]
Message-ID: <87cy1q5724.fsf@suse.de> (raw)
In-Reply-To: <CAFEAcA9+GzKxWKLcWvT5e2voO0mRR5jaKfXk4JrhWU6jFGXpNA@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Fri, 27 Feb 2026 at 18:57, Fabiano Rosas <farosas@suse.de> wrote:
>>
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>
>> > Running "make check" with the clang leak sanitizer reveals some
>> > leak reports which are either not our problem or else not
>> > a leak which is worth our time to fix. Add some suppressions
>> > for these.
>> >
>> > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>>
>> Reviewed-by: Fabiano Rosas <farosas@suse.de>
>>
>> FYI, mine has these. The first one is on my list to fix once I find some
>> time. The last two seem to be part of the stack for the ones you added
>> here.
>>
>> leak:qcrypto_tls_session_push
>> leak:gnutls_handshake
>> leak:memory_region_do_init
>> leak:qos_traverse_graph
>> leak:qdev_get_named_gpio_list
>
> qdev_get_named_gpio_list is definitely used in paths other than
> the qemu_irq_intercept_in one we want to hit.
>
> I think that recent memory region fixes ought to have fixed the
> ones you're suppressing with memory_region_do_init.
>
> I couldn't make any sense of the qos_traverse_graph/walk_path one:
> it seems to be related to the qtest "subprocess" functionality
> somehow and doesn't repro without that.
>
Ahh I remember this... Here, patch 5/6:
https://lore.kernel.org/r/20241209204427.17763-1-farosas@suse.de
> thanks
> -- PMM
next prev parent reply other threads:[~2026-02-27 19:19 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 [this message]
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 ` [PATCH 0/4] arm: Fix some memory leaks Fabiano Rosas
2026-02-27 19:01 ` 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=87cy1q5724.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.