All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: guillaume vincke <guillaume.vincke@ovhcloud.com>
Cc: armbru@redhat.com,
	Richard Henderson <richard.henderson@linaro.org>,
	 qemu-devel@nongnu.org
Subject: Re: [PULL 0/8] NBD patches through 2026-11-10
Date: Fri, 13 Nov 2026 07:57:39 -0600	[thread overview]
Message-ID: <avcWw34WAJKerP2L@redhat.com> (raw)
In-Reply-To: <ff4c1e4d-cb1b-4c61-ad2e-537131c45dd9@ovhcloud.com>

On Fri, Nov 13, 2026 at 09:12:09AM +0100, guillaume vincke wrote:
> > > Markus, what are your thoughts on a QMP addition this late into 11.2
> > > so that the test in 2/8 can be stable? I'm torn on whether the NBD bug
> > > in 1/8 is severe enough to need to go in 11.2.0 proper, or whether the
> > > bug is weak enough that it is safer to wait until 11.2.1 via the
> > > qemu-stable process.  Patches 3-8 fix CVEs, so they definitely belong
> > > in 11.2.
> > 
> > "Only bug fixes" since soft freeze.  The closer we get to the release,
> > the more serious the bugs need to be.
> > 
> > Including tests with the bug fixes feels okay to me.  Test
> > infrastructure in QEMU proper, like a QMP command, is pushing it,
> > though.
> > 
> > What's the impact of omitting or disabling the troublesome test until
> > after the release?
> 
> In my opinion, the 1/8 fix and the associated 2/8 test can be postponed
> to the next release. That behavior has been there for a long time and,
> as far as I know, nobody but me has complained about it. Taking the
> time to get a robust test in is probably the safer option.

That settles it. I'm saving both Guillame's bug fix and the unit test
for 12.0 when we can also pick up the QMP changes to make the unit
test robust; and planning a strong possibility of backporting the bug
fix, but not the unit test, to 11.2.1 once the 11.2 release is out.  I
will respin this pull request accordingly.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org



      reply	other threads:[~2026-11-13 13:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  3:51 [PULL 0/8] NBD patches through 2026-11-10 Eric Blake
2026-11-11  3:51 ` [PULL 1/8] nbd/client-connection: Fix client returning a closed channel Eric Blake
2026-11-11  3:51 ` [PULL 2/8] iotests: Add coverage for NBD connect thread start delay Eric Blake
2026-11-11  3:51 ` [PULL 3/8] docs: Mention security considerations for NBD Eric Blake
2026-11-11  3:51 ` [PULL 4/8] iotests: Refactor python NBD server setup Eric Blake
2026-11-11  3:51 ` [PULL 5/8] nbd/server: Reject rather than assert on non-compliant BLOCK_STATUS Eric Blake
2026-11-11  3:51 ` [PULL 6/8] iotests: Add new nbd-robustness test Eric Blake
2026-11-11  3:51 ` [PULL 7/8] nbd/server: Reject rather than assert on non-compliant NBD_OPT_SET_META_CONTEXT Eric Blake
2026-11-11  3:51 ` [PULL 8/8] iotests: Add another nbd-robustness test Eric Blake
2026-11-12 18:16 ` [PULL 0/8] NBD patches through 2026-11-10 Richard Henderson
2026-11-12 19:27   ` Eric Blake
2026-11-13  5:47     ` Markus Armbruster
2026-11-13  8:12       ` guillaume vincke
2026-11-13 13:57         ` 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=avcWw34WAJKerP2L@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=guillaume.vincke@ovhcloud.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.