From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL v2 0/3] NBD patches through 2020-06-09
Date: Wed, 10 Jun 2020 13:05:10 -0500 [thread overview]
Message-ID: <20200610180514.3751958-1-eblake@redhat.com> (raw)
The following changes since commit 31d321c2b3574dcc74e9f6411af06bca6b5d10f4:
Merge remote-tracking branch 'remotes/philmd-gitlab/tags/sparc-next-20200609' into staging (2020-06-09 17:29:47 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2020-06-09-v2
for you to fetch changes up to 5c86bdf1208916ece0b87e1151c9b48ee54faa3e:
block: Call attention to truncation of long NBD exports (2020-06-10 12:58:59 -0500)
In v2: patch 2 adjusted per review (only sending the changed patch)
----------------------------------------------------------------
NBD patches for 2020-06-09
- fix iotest 194 race
- fix CVE-2020-10761: server DoS from assertion on long NBD error messages
----------------------------------------------------------------
Eric Blake (2):
nbd/server: Avoid long error message assertions CVE-2020-10761
block: Call attention to truncation of long NBD exports
Vladimir Sementsov-Ogievskiy (1):
iotests: 194: wait for migration completion on target too
block.c | 7 +++++--
block/nbd.c | 21 +++++++++++++--------
nbd/server.c | 23 ++++++++++++++++++++---
tests/qemu-iotests/143 | 4 ++++
tests/qemu-iotests/143.out | 2 ++
tests/qemu-iotests/194 | 10 ++++++++++
tests/qemu-iotests/194.out | 5 +++++
7 files changed, 59 insertions(+), 13 deletions(-)
--
2.27.0
next reply other threads:[~2020-06-10 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 18:05 Eric Blake [this message]
2020-06-10 18:05 ` [PULL v2 2/3] nbd/server: Avoid long error message assertions CVE-2020-10761 Eric Blake
2020-06-11 21:36 ` [PULL v2 0/3] NBD patches through 2020-06-09 Peter Maydell
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=20200610180514.3751958-1-eblake@redhat.com \
--to=eblake@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).