From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PULL 02/10] io: Fix TLS bye task leak
Date: Thu, 19 Mar 2026 08:57:26 +0000 [thread overview]
Message-ID: <abu6drYEygCgA0R9@redhat.com> (raw)
In-Reply-To: <f6c365e9-7d4e-4ad5-afc3-1fe31230baae@tls.msk.ru>
On Wed, Mar 18, 2026 at 11:36:50PM +0300, Michael Tokarev wrote:
> On 17.03.2026 21:23, Fabiano Rosas wrote:
> > Recent fixes to TLS tasks memory handling have left the TLS bye task
> > uncovered. Fix by freeing the task in the same way the handshake task
> > is freed.
> >
> > Direct leak of 704 byte(s) in 4 object(s) allocated from:
> > #1 0x7f5909b1d6a0 in g_malloc0 ../glib/gmem.c:163
> > #2 0x557650496d61 in qio_task_new ../io/task.c:58:12
> > #3 0x557650475d7f in qio_channel_tls_bye ../io/channel-tls.c:352:12
> > #4 0x55764f7a1bb4 in migration_tls_channel_end ../migration/tls.c:159:5
> > #5 0x55764f709750 in migration_ioc_shutdown_gracefully ../migration/multifd.c:462:9
> > #6 0x55764f6fcf53 in multifd_send_terminate_threads ../migration/multifd.c:493:13
> > #7 0x55764f6fcafb in multifd_send_shutdown ../migration/multifd.c:580:5
> > #8 0x55764f6e1b14 in migration_cleanup ../migration/migration.c:1323:9
> > #9 0x55764f6f5bac in migration_cleanup_bh ../migration/migration.c:1350:5
> >
> > Fixes: d39d0f3acd ("io: fix cleanup for TLS I/O source data on cancellation")
> > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> > Acked-by: Daniel P. Berrangé <berrange@redhat.com>
> > Link: https://lore.kernel.org/qemu-devel/20260311213418.16951-3-farosas@suse.de
> > Signed-off-by: Fabiano Rosas <farosas@suse.de>
>
> This seems like a qemu-stable material, -- since the above mentioned
> commit is in currently active stable branches.
>
> Please let me know if I shouldn't pick it up for the currently active
> stable branches (10.0 & 10.2).
Yes, please take to stable.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-03-19 8:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 18:23 [PULL 00/10] Migration/Qtest patches for 2026-03-17 Fabiano Rosas
2026-03-17 18:23 ` [PULL 01/10] tests/qtest/migration: Fix leak of migration tests data Fabiano Rosas
2026-03-17 18:23 ` [PULL 02/10] io: Fix TLS bye task leak Fabiano Rosas
2026-03-18 20:36 ` Michael Tokarev
2026-03-19 8:57 ` Daniel P. Berrangé [this message]
2026-03-17 18:23 ` [PULL 03/10] tests/qtest/migration: Fix leak in CPR exec test Fabiano Rosas
2026-03-17 18:23 ` [PULL 04/10] migration/multifd: Fix leaks of TLS error objects Fabiano Rosas
2026-03-17 18:23 ` [PULL 05/10] tests/qtest/migration: Force exit-on-error=false Fabiano Rosas
2026-03-26 9:02 ` Thomas Huth
2026-03-26 13:28 ` Fabiano Rosas
2026-03-17 18:23 ` [PULL 06/10] migration: assert that the same migration handler is not being added twice Fabiano Rosas
2026-03-17 18:23 ` [PULL 07/10] migration/options: Fix leaks in StrOrNull qdev accessors Fabiano Rosas
2026-03-17 18:23 ` [PULL 08/10] migration: fix implicit integer division in migration_update_counters Fabiano Rosas
2026-03-17 18:23 ` [PULL 09/10] tests/qtest: Don't dup machine name in qtest_cb_for_every_machine callbacks Fabiano Rosas
2026-03-17 18:23 ` [PULL 10/10] tests/qtest/test-hmp: Free machine options Fabiano Rosas
2026-03-18 13:26 ` [PULL 00/10] Migration/Qtest patches for 2026-03-17 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=abu6drYEygCgA0R9@redhat.com \
--to=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=mjt@tls.msk.ru \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.