From: Peter Maydell <peter.maydell@linaro.org>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: "Mauro Matteo Cascella" <mcascell@redhat.com>,
"Prasad J Pandit" <pjp@fedoraproject.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Yuval Shaia" <yuval.shaia.ml@gmail.com>,
vv474172261@gmail.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PULL V2 0/3] PVRDMA queue
Date: Mon, 5 Jul 2021 12:44:42 +0100 [thread overview]
Message-ID: <CAFEAcA8ZPPpSNvb8W+HGXj4N4qQ-ApoePKhjMnBHkrKdrmRpwg@mail.gmail.com> (raw)
In-Reply-To: <20210704205255.27124-1-marcel.apfelbaum@gmail.com>
On Sun, 4 Jul 2021 at 21:52, Marcel Apfelbaum
<marcel.apfelbaum@gmail.com> wrote:
>
> The following changes since commit 9c2647f75004c4f7d64c9c0ec55f8c6f0739a8b1:
>
> Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2021-07-02 11:46:32 +0100)
>
> are available in the Git repository at:
>
> https://github.com/marcel-apf/qemu tags/pvrdma-04-07-2021-v2
>
> for you to fetch changes up to 66ae37d8cc313f89272e711174a846a229bcdbd3:
>
> pvrdma: Fix the ring init error flow (CVE-2021-3608) (2021-07-04 22:47:51 +0300)
>
> ----------------------------------------------------------------
> PVRDMA queue
>
> Several CVE fixes for the PVRDMA device.
>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.1
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2021-07-05 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 20:52 [PULL V2 0/3] PVRDMA queue Marcel Apfelbaum
2021-07-04 20:52 ` [PULL V2 1/3] hw/rdma: Fix possible mremap overflow in the pvrdma device (CVE-2021-3582) Marcel Apfelbaum
2021-07-04 20:52 ` [PULL V2 2/3] pvrdma: Ensure correct input on ring init (CVE-2021-3607) Marcel Apfelbaum
2021-07-04 20:52 ` [PULL V2 3/3] pvrdma: Fix the ring init error flow (CVE-2021-3608) Marcel Apfelbaum
2021-07-05 11:44 ` Peter Maydell [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=CAFEAcA8ZPPpSNvb8W+HGXj4N4qQ-ApoePKhjMnBHkrKdrmRpwg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mcascell@redhat.com \
--cc=philmd@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-devel@nongnu.org \
--cc=vv474172261@gmail.com \
--cc=yuval.shaia.ml@gmail.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).