All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Steve Sistare <steven.sistare@oracle.com>, qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Eduardo Habkost <eduardo@habkost.net>,
	Philippe Mathieu-Daude <philmd@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Steve Sistare <steven.sistare@oracle.com>
Subject: Re: [PATCH V6 00/24] Live update: cpr-transfer
Date: Wed, 15 Jan 2025 11:52:21 -0300	[thread overview]
Message-ID: <87bjw8f7tm.fsf@suse.de> (raw)
In-Reply-To: <87plkpf8bn.fsf@suse.de>

Fabiano Rosas <farosas@suse.de> writes:

> Hi Steve,
>
> The CI shows some issues, please take a look:
>
> https://gitlab.com/farosas/qemu/-/pipelines/1624984802

The asan build is also upset:

../configure --target-list=x86_64-softmmu --disable-docs \
--python=/usr/bin/python3.11 --disable-plugins --enable-debug \
--enable-asan --cc=clang

QTEST_QEMU_BINARY=../build/qemu-system-x86_64 \
./tests/qtest/migration-test -p /x86_64/migration/mode/transfer


Direct leak of 392 byte(s) in 1 object(s) allocated from:                                                                                                                                      
    ...
    #2 0x5607648c3fd0 in object_new ../qom/object.c:789:12
    #3 0x5607649a3da3 in qio_channel_socket_new ../io/channel-socket.c:64:31            
    #4 0x560763f59845 in cpr_transfer_output ../migration/cpr-transfer.c:28:34

Direct leak of 392 byte(s) in 1 object(s) allocated from:
    ...
    #2 0x55dfe6727fd0 in object_new ../qom/object.c:789:12
    #3 0x55dfe6807da3 in qio_channel_socket_new ../io/channel-socket.c:64:31

Direct leak of 120 byte(s) in 5 object(s) allocated from:
    ...
    #2 0x55dfe67fc671 in qemu_peek_byte ../migration/qemu-file.c:777:9

Direct leak of 104 byte(s) in 1 object(s) allocated from:
    ...
    #2 0x55dfe6727fd0 in object_new ../qom/object.c:789:12
    #3 0x55dfe6825e0f in qio_net_listener_new ../io/net-listener.c:29:29
    #4 0x55dfe5dbdad4 in cpr_transfer_input ../migration/cpr-transfer.c:57:36

Direct leak of 24 byte(s) in 1 object(s) allocated from:
    ...
    #2 0x55dfe67fc671 in qemu_peek_byte ../migration/qemu-file.c:777:9
    #3 0x55dfe67fc7ad in qemu_get_byte ../migration/qemu-file.c:790:14
    #4 0x55dfe67ffc1b in qemu_get_be32 ../migration/qemu-file.c:840:23
    #5 0x55dfe5dbc584 in cpr_state_load ../migration/cpr.c:189:9


  parent reply	other threads:[~2025-01-15 14:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 17:23 [PATCH V6 00/24] Live update: cpr-transfer Steve Sistare
2025-01-14 17:23 ` [PATCH V6 01/24] backends/hostmem-shm: factor out allocation of "anonymous shared memory with an fd" Steve Sistare
2025-01-14 17:23 ` [PATCH V6 02/24] physmem: fix qemu_ram_alloc_from_fd size calculation Steve Sistare
2025-01-14 17:23 ` [PATCH V6 03/24] physmem: qemu_ram_alloc_from_fd extensions Steve Sistare
2025-01-14 17:30   ` Peter Xu
2025-01-14 17:23 ` [PATCH V6 04/24] physmem: fd-based shared memory Steve Sistare
2025-01-14 17:23 ` [PATCH V6 05/24] memory: add RAM_PRIVATE Steve Sistare
2025-01-14 17:23 ` [PATCH V6 06/24] machine: aux-ram-share option Steve Sistare
2025-01-14 17:23 ` [PATCH V6 07/24] migration: cpr-state Steve Sistare
2025-01-14 17:23 ` [PATCH V6 08/24] physmem: preserve ram blocks for cpr Steve Sistare
2025-01-14 17:23 ` [PATCH V6 09/24] hostmem-memfd: preserve " Steve Sistare
2025-01-14 17:23 ` [PATCH V6 10/24] hostmem-shm: " Steve Sistare
2025-01-14 17:23 ` [PATCH V6 11/24] migration: enhance migrate_uri_parse Steve Sistare
2025-01-14 17:23 ` [PATCH V6 12/24] migration: incoming channel Steve Sistare
2025-01-14 17:23 ` [PATCH V6 13/24] migration: SCM_RIGHTS for QEMUFile Steve Sistare
2025-01-14 17:23 ` [PATCH V6 14/24] migration: VMSTATE_FD Steve Sistare
2025-01-14 17:23 ` [PATCH V6 15/24] migration: cpr-transfer save and load Steve Sistare
2025-01-14 17:23 ` [PATCH V6 16/24] migration: cpr-transfer mode Steve Sistare
2025-01-14 17:23 ` [PATCH V6 17/24] migration-test: memory_backend Steve Sistare
2025-01-14 17:23 ` [PATCH V6 18/24] tests/qtest: optimize migrate_set_ports Steve Sistare
2025-01-14 17:23 ` [PATCH V6 19/24] tests/qtest: defer connection Steve Sistare
2025-01-14 17:23 ` [PATCH V6 20/24] migration-test: " Steve Sistare
2025-01-14 17:23 ` [PATCH V6 21/24] tests/qtest: enhance migration channels Steve Sistare
2025-01-14 17:23 ` [PATCH V6 22/24] tests/qtest: assert qmp connected Steve Sistare
2025-01-14 17:30   ` Peter Xu
2025-01-14 17:23 ` [PATCH V6 23/24] migration-test: cpr-transfer Steve Sistare
2025-01-14 17:23 ` [PATCH V6 24/24] migration: cpr-transfer documentation Steve Sistare
2025-01-14 17:38 ` [PATCH V6 00/24] Live update: cpr-transfer Steven Sistare
2025-01-14 17:39   ` Steven Sistare
2025-01-14 20:29 ` Fabiano Rosas
2025-01-14 21:14   ` Steven Sistare
2025-01-14 21:37     ` Steven Sistare
2025-01-15 14:05       ` Steven Sistare
2025-01-15 14:52   ` Fabiano Rosas [this message]
2025-01-15 17:54     ` Steven Sistare

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=87bjw8f7tm.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=david@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=steven.sistare@oracle.com \
    /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.