From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
John Snow <jsnow@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Prasad J Pandit" <pjp@fedoraproject.org>,
qemu-block@nongnu.org, "Darren Kenny" <darren.kenny@oracle.com>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Hanna Reitz" <hreitz@redhat.com>,
"Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [PATCH-for-6.2 0/2] hw/block/fdc: Fix CVE-2021-3507
Date: Mon, 22 Nov 2021 15:54:56 +0100 [thread overview]
Message-ID: <a67ccbe8-7701-ee38-5e5c-a65f60f33f20@redhat.com> (raw)
In-Reply-To: <20211118115733.4038610-1-philmd@redhat.com>
ping for 6.2?
On 11/18/21 12:57, Philippe Mathieu-Daudé wrote:
> Trivial fix for CVE-2021-3507.
>
> Philippe Mathieu-Daudé (2):
> hw/block/fdc: Prevent end-of-track overrun (CVE-2021-3507)
> tests/qtest/fdc-test: Add a regression test for CVE-2021-3507
>
> hw/block/fdc.c | 8 ++++++++
> tests/qtest/fdc-test.c | 20 ++++++++++++++++++++
> 2 files changed, 28 insertions(+)
>
next prev parent reply other threads:[~2021-11-22 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 11:57 [PATCH-for-6.2 0/2] hw/block/fdc: Fix CVE-2021-3507 Philippe Mathieu-Daudé
2021-11-18 11:57 ` [PATCH-for-6.2 1/2] hw/block/fdc: Prevent end-of-track overrun (CVE-2021-3507) Philippe Mathieu-Daudé
2021-11-23 15:56 ` Hanna Reitz
2021-11-18 11:57 ` [PATCH-for-6.2 2/2] tests/qtest/fdc-test: Add a regression test for CVE-2021-3507 Philippe Mathieu-Daudé
2021-11-23 16:04 ` Alexander Bulekov
2021-11-23 16:08 ` Hanna Reitz
2021-11-24 23:27 ` John Snow
2021-11-22 14:54 ` Philippe Mathieu-Daudé [this message]
2022-01-27 20:14 ` [PATCH-for-6.2 0/2] hw/block/fdc: Fix CVE-2021-3507 Jon Maloy
2022-02-04 21:39 ` John Snow
2022-02-06 19:15 ` Jon Maloy
2022-02-06 19:19 ` Jon Maloy
2022-03-10 17:14 ` Thomas Huth
2022-03-10 17:53 ` Jon Maloy
2022-03-18 18:50 ` Thomas Huth
2022-03-23 2:25 ` John Snow
2022-05-03 9:59 ` Kevin Wolf
2022-05-03 16:21 ` Jon Maloy
2022-05-12 11:06 ` Kevin Wolf
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=a67ccbe8-7701-ee38-5e5c-a65f60f33f20@redhat.com \
--to=philmd@redhat.com \
--cc=alxndr@bu.edu \
--cc=darren.kenny@oracle.com \
--cc=hpoussin@reactos.org \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).