From: Juan Quintela <quintela@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, dgilbert@redhat.com,
qemu-devel@nongnu.org, rjones@redhat.com,
marcandre.lureau@redhat.com, armbru@redhat.com,
philmd@linaro.org, berrange@redhat.com
Subject: Re: [PATCH v4] test-vmstate: fix bad GTree usage, use-after-free
Date: Tue, 28 Feb 2023 11:41:12 +0100 [thread overview]
Message-ID: <87fsaqm5rr.fsf@secure.mitica> (raw)
In-Reply-To: <20230228092944.341317-1-eric.auger@redhat.com> (Eric Auger's message of "Tue, 28 Feb 2023 10:29:44 +0100")
Eric Auger <eric.auger@redhat.com> wrote:
> According to g_tree_foreach() documentation:
> "The tree may not be modified while iterating over it (you can't
> add/remove items)."
>
> compare_trees()/diff_tree() fail to respect this rule.
> Historically GLib2 used a slice allocator for the GTree APIs
> which did not immediately release the memory back to the system
> allocator. As a result QEMU's use-after-free bug was not visible.
> With GLib > 2.75.3 however, GLib2 has switched to using malloc
> and now a SIGSEGV can be observed while running test-vmstate.
>
> Get rid of the node removal within the tree traversal. Also
> check the trees have the same number of nodes before the actual
> diff.
>
> Fixes: 9a85e4b8f6 ("migration: Support gtree migration")
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1518
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Reported-by: Richard W.M. Jones <rjones@redhat.com>
> Tested-by: Richard W.M. Jones <rjones@redhat.com>
> Reviewed-by: Richard W.M. Jones <rjones@redhat.com>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
queued.
prev parent reply other threads:[~2023-02-28 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:29 [PATCH v4] test-vmstate: fix bad GTree usage, use-after-free Eric Auger
2023-02-28 10:41 ` Juan Quintela [this message]
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=87fsaqm5rr.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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.