From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, "Amit Shah" <amit@kernel.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH-for-9.0 v2 0/4] hw/virtio: Protect from more DMA re-entrancy bugs
Date: Tue, 9 Apr 2024 16:35:47 +0200 [thread overview]
Message-ID: <250524f6-14bf-4fb1-8efc-e562c1d1c857@linaro.org> (raw)
In-Reply-To: <20240409073320-mutt-send-email-mst@kernel.org>
On 9/4/24 13:33, Michael S. Tsirkin wrote:
> On Tue, Apr 09, 2024 at 12:55:33PM +0200, Philippe Mathieu-Daudé wrote:
>> Fixes for CVE-2024-3446.
>>
>> Gerd suggested to use the transport guard to protect the
>> device from DMA re-entrancy abuses.
>>
>> Since v1:
>> - Take a DeviceState argument, not VirtIODevice, so it
>> works seamlessly with CCW devices (actually the original
>> code from Gerd).
>> - Build and test :>
>>
>> I'll send a PR with these patches later today.
>
> I reviewed these too now
>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Thanks, series queued.
prev parent reply other threads:[~2024-04-09 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 10:55 [PATCH-for-9.0 v2 0/4] hw/virtio: Protect from more DMA re-entrancy bugs Philippe Mathieu-Daudé
2024-04-09 10:55 ` [PATCH-for-9.0 v2 1/4] hw/virtio: Introduce virtio_bh_new_guarded() helper Philippe Mathieu-Daudé
2024-04-09 10:55 ` [PATCH-for-9.0 v2 2/4] hw/display/virtio-gpu: Protect from DMA re-entrancy bugs Philippe Mathieu-Daudé
2024-04-09 10:55 ` [PATCH-for-9.0 v2 3/4] hw/char/virtio-serial-bus: " Philippe Mathieu-Daudé
2024-04-09 10:55 ` [PATCH-for-9.0 v2 4/4] hw/virtio/virtio-crypto: " Philippe Mathieu-Daudé
2024-04-09 11:33 ` [PATCH-for-9.0 v2 0/4] hw/virtio: Protect from more " Michael S. Tsirkin
2024-04-09 14:35 ` Philippe Mathieu-Daudé [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=250524f6-14bf-4fb1-8efc-e562c1d1c857@linaro.org \
--to=philmd@linaro.org \
--cc=amit@kernel.org \
--cc=arei.gonglei@huawei.com \
--cc=kraxel@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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 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).