From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [PULL 0/3] NBD patches through 2020-06-09
Date: Wed, 10 Jun 2020 08:18:29 -0500 [thread overview]
Message-ID: <0b58576a-593b-68ec-df80-26ad7dec4d42@redhat.com> (raw)
In-Reply-To: <20200610011713.3687895-1-eblake@redhat.com>
On 6/9/20 8:17 PM, Eric Blake wrote:
> 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
>
> for you to fetch changes up to 2886df0c75c1c5f6aed054c54f4ad48aeee04bfd:
>
> block: Call attention to truncation of long NBD exports (2020-06-09 17:05:50 -0500)
>
> ----------------------------------------------------------------
> 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
Vladimir raised a potential thread-safety issue in this patch. As it is
intended to fix a CVE, let's hold off on this pull request, and I'll
send a v2 once I have better review.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2020-06-10 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 1:17 [PULL 0/3] NBD patches through 2020-06-09 Eric Blake
2020-06-10 1:17 ` [PULL 1/3] iotests: 194: wait for migration completion on target too Eric Blake
2020-06-10 1:17 ` [PULL 2/3] nbd/server: Avoid long error message assertions CVE-2020-10761 Eric Blake
2020-06-10 1:17 ` [PULL 3/3] block: Call attention to truncation of long NBD exports Eric Blake
2020-06-10 13:18 ` Eric Blake [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=0b58576a-593b-68ec-df80-26ad7dec4d42@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).