From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: damien.hedde@greensocs.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [PATCH] qdev-monitor: Fix use after free on duplicate device ID error
Date: Wed, 3 Nov 2021 10:33:41 +0100 [thread overview]
Message-ID: <YYJXddA/gDbtR0Zf@redhat.com> (raw)
In-Reply-To: <20211103073848.1459138-1-armbru@redhat.com>
Am 03.11.2021 um 08:38 hat Markus Armbruster geschrieben:
> Fixes: 4a1d937796de0fecd8b22d7dbebf87f38e8282fd
> Reported-by: Coverity CID 1465223
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Stefan already sent a patch yesterday:
https://lists.gnu.org/archive/html/qemu-devel/2021-11/msg00759.html
Message-Id: <20211102163342.31162-1-stefanha@redhat.com>
Kevin
prev parent reply other threads:[~2021-11-03 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 7:38 [PATCH] qdev-monitor: Fix use after free on duplicate device ID error Markus Armbruster
2021-11-03 7:42 ` Marc-André Lureau
2021-11-03 9:25 ` Damien Hedde
2021-11-03 9:33 ` Kevin Wolf [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=YYJXddA/gDbtR0Zf@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=damien.hedde@greensocs.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).