From: Eric Blake <eblake@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, QEMU Stable <qemu-stable@nongnu.org>
Subject: Re: [PULL v2 0/6] NBD patches through 2026-11-10
Date: Mon, 16 Nov 2026 10:16:31 -0600 [thread overview]
Message-ID: <avsrzudnvwGrMLc2@redhat.com> (raw)
In-Reply-To: <b3079073-8de6-4a4a-af89-256c2a4bf351@tls.msk.ru>
On Sat, Nov 14, 2026 at 09:27:02PM +0300, Michael Tokarev wrote:
> > ----------------------------------------------------------------
> > Eric Blake (6):
> > docs: Mention security considerations for NBD
> > iotests: Refactor python NBD server setup
> > nbd/server: Reject rather than assert on non-compliant BLOCK_STATUS
> > iotests: Add new nbd-robustness test
> > nbd/server: Reject rather than assert on non-compliant NBD_OPT_SET_META_CONTEXT
> > iotests: Add another nbd-robustness test
> I'm picking up this whole Pull Request to the stable qemu series, -
> besides 2 fixes it includes the tests and the documentation update.
>
> Please let me know if I should not :)
While the two patches for the CVE fixes are essential, I see no
problem with the rest of the series also going into stable. Testing
that a CVE fix works even in the backport always sounds reasonable to
me! And the doc update is useful information on best practices for
minimizing security risks.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
prev parent reply other threads:[~2026-11-16 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 14:30 [PULL v2 0/6] NBD patches through 2026-11-10 Eric Blake
2026-11-13 14:30 ` [PULL v2 1/6] docs: Mention security considerations for NBD Eric Blake
2026-11-13 14:30 ` [PULL v2 2/6] iotests: Refactor python NBD server setup Eric Blake
2026-11-13 14:30 ` [PULL v2 3/6] nbd/server: Reject rather than assert on non-compliant BLOCK_STATUS Eric Blake
2026-11-13 14:30 ` [PULL v2 4/6] iotests: Add new nbd-robustness test Eric Blake
2026-11-13 14:30 ` [PULL v2 5/6] nbd/server: Reject rather than assert on non-compliant NBD_OPT_SET_META_CONTEXT Eric Blake
2026-11-13 14:30 ` [PULL v2 6/6] iotests: Add another nbd-robustness test Eric Blake
2026-11-13 19:02 ` [PULL v2 0/6] NBD patches through 2026-11-10 Richard Henderson
2026-11-14 18:27 ` Michael Tokarev
2026-11-16 16:16 ` 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=avsrzudnvwGrMLc2@redhat.com \
--to=eblake@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.