From: Albert Esteve <aesteve@redhat.com>
To: Dorinda Bassey <dbassey@redhat.com>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
qemu-devel@nongnu.org, marcandre.lureau@redhat.com,
Michael Tsirkin <mst@redhat.com>
Subject: Re: [PATCH v2] virtio-dmabuf: Ensure UUID persistence for hash table insertion
Date: Mon, 15 Sep 2025 11:23:32 +0200 [thread overview]
Message-ID: <CADSE00LnkhQtTbnWgxMyOcMU+NsB_UnHTJyDWvXQf31Nwvr9Ow@mail.gmail.com> (raw)
In-Reply-To: <CACzuRyy5urdAzPqRQ__VOZ6R-43LKLFzqj1w_+hsZYs+ovHxtg@mail.gmail.com>
On Mon, Sep 15, 2025 at 11:16 AM Dorinda Bassey <dbassey@redhat.com> wrote:
>
> Hi Albert and Michael,
>
> seems this patch fell through the cracks, It was posted but never picked up. Could you help push it? thanks!
I do not remember this patch! Great that you checked, as this fixes a
legitimate issue. Hopefully will get integrated this time.
>
> BR,
> Dorinda.
>
> On Fri, Nov 8, 2024 at 10:29 AM Stefano Garzarella <sgarzare@redhat.com> wrote:
>>
>> On Thu, Nov 07, 2024 at 07:00:31PM +0100, Dorinda Bassey wrote:
>> >In `virtio_add_resource` function, the UUID used as a key for
>> >`g_hash_table_insert` was temporary, which could lead to
>> >invalid lookups when accessed later. This patch ensures that
>> >the UUID remains valid by duplicating it into a newly allocated
>> >memory space. The value is then inserted into the hash table
>> >with this persistent UUID key to ensure that the key stored in
>> >the hash table remains valid as long as the hash table entry
>> >exists.
>> >
>> >Fixes: faefdba847 ("hw/display: introduce virtio-dmabuf")
>> >
>> >Signed-off-by: Dorinda Bassey <dbassey@redhat.com>
>> >---
>> > hw/display/virtio-dmabuf.c | 6 ++++--
>> > 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Reviewed-by: Albert Esteve <aesteve@redhat.com>
>>
>> >
>> >diff --git a/hw/display/virtio-dmabuf.c b/hw/display/virtio-dmabuf.c
>> >index 3dba4577ca7..5e0395be77c 100644
>> >--- a/hw/display/virtio-dmabuf.c
>> >+++ b/hw/display/virtio-dmabuf.c
>> >@@ -35,11 +35,13 @@ static bool virtio_add_resource(QemuUUID *uuid, VirtioSharedObject *value)
>> > if (resource_uuids == NULL) {
>> > resource_uuids = g_hash_table_new_full(qemu_uuid_hash,
>> > uuid_equal_func,
>> >- NULL,
>> >+ g_free,
>> > g_free);
>> > }
>> > if (g_hash_table_lookup(resource_uuids, uuid) == NULL) {
>> >- g_hash_table_insert(resource_uuids, uuid, value);
>> >+ g_hash_table_insert(resource_uuids,
>> >+ g_memdup2(uuid, sizeof(*uuid)),
>> >+ value);
>> > } else {
>> > result = false;
>> > }
>> >--
>> >2.47.0
>> >
>>
prev parent reply other threads:[~2025-09-15 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 18:00 [PATCH v2] virtio-dmabuf: Ensure UUID persistence for hash table insertion Dorinda Bassey
2024-11-08 9:29 ` Stefano Garzarella
2025-09-15 9:16 ` Dorinda Bassey
2025-09-15 9:23 ` Albert Esteve [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=CADSE00LnkhQtTbnWgxMyOcMU+NsB_UnHTJyDWvXQf31Nwvr9Ow@mail.gmail.com \
--to=aesteve@redhat.com \
--cc=dbassey@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).