From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
Max Reitz <mreitz@redhat.com>, Klaus Jensen <its@irrelevant.dk>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCH for-6.0? 0/1] hw/block/nvme: fix msix uninit
Date: Thu, 22 Apr 2021 15:58:33 +0200 [thread overview]
Message-ID: <20210422135834.406688-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Hi Peter,
The commit message on the patch describes the issue. This is a QEMU
crashing bug in -rc4 that I introduced early in the cycle and never
found in time. Lack of testing device hotplugging is the cause for that.
I'm not sure what to say other than I'm terribly sorry for introducing
this and if this means an -rc5 needs to be rolled, then I'm even more
sorry.
I think an acceptance test could have caught this, and I am already
working on an acceptance test suite for the nvme device, so I'll add
something that test this as well. But, well, it doesn't help now.
Klaus Jensen (1):
hw/block/nvme: fix invalid msix exclusive uninit
hw/block/nvme.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.31.1
next reply other threads:[~2021-04-22 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 13:58 Klaus Jensen [this message]
2021-04-22 13:58 ` [PATCH for-6.0? 1/1] hw/block/nvme: fix invalid msix exclusive uninit Klaus Jensen
2021-04-22 15:40 ` Klaus Jensen
2021-04-22 14:07 ` [PATCH for-6.0? 0/1] hw/block/nvme: fix msix uninit Klaus Jensen
2021-04-22 18:58 ` Peter Maydell
2021-04-22 19:17 ` Klaus Jensen
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=20210422135834.406688-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--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 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.