Peter Maydell <[email protected]> writes: > On Fri, 27 Feb 2026 at 18:57, Fabiano Rosas <[email protected]> wrote: >> >> Peter Maydell <[email protected]> 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 <[email protected]> >> >> Reviewed-by: Fabiano Rosas <[email protected]> >> >> 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/[email protected] > thanks > -- PMM
