From: Alexander Graf <agraf@csgraf.de>
To: Klaus Jensen <its@irrelevant.dk>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
Max Reitz <mreitz@redhat.com>,
Minwoo Im <minwoo.im.dev@gmail.com>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] hw/block/nvme: fix legacy namespace registration
Date: Thu, 11 Feb 2021 13:34:56 +0100 [thread overview]
Message-ID: <280b4e29-1337-dac7-071c-1feeab182294@csgraf.de> (raw)
In-Reply-To: <20210211105451.937713-1-its@irrelevant.dk>
On 11.02.21 11:54, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> Moving namespace registration to the nvme-ns realization function had
> the unintended side-effect of breaking legacy namespace registration.
> Fix this.
>
> Fixes: 15d024d4aa9b ("hw/block/nvme: split setup and register for namespace")
> Reported-by: Alexander Graf <agraf@csgraf.de>
> Cc: Minwoo Im <minwoo.im.dev@gmail.com>
> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
I can confirm that this fixes the upstream regression. Thanks a lot.
Please work on a way with Peter to pull this into the tree as quickly as
possible, so that we maintain a working master branch with NVMe.
Tested-by: Alexander Graf <agraf@csgraf.de>
Thanks!
Alex
> ---
> hw/block/nvme.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/hw/block/nvme.c b/hw/block/nvme.c
> index 5ce21b7100b3..d36e14fe13e2 100644
> --- a/hw/block/nvme.c
> +++ b/hw/block/nvme.c
> @@ -4507,6 +4507,12 @@ static void nvme_realize(PCIDevice *pci_dev, Error **errp)
> if (nvme_ns_setup(ns, errp)) {
> return;
> }
> +
> + if (nvme_register_namespace(n, ns, errp)) {
> + error_propagate_prepend(errp, local_err,
> + "could not register namespace: ");
> + return;
> + }
> }
> }
>
next prev parent reply other threads:[~2021-02-11 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 10:54 [PATCH] hw/block/nvme: fix legacy namespace registration Klaus Jensen
2021-02-11 12:34 ` Alexander Graf [this message]
2021-02-11 13:10 ` Minwoo Im
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=280b4e29-1337-dac7-071c-1feeab182294@csgraf.de \
--to=agraf@csgraf.de \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=minwoo.im.dev@gmail.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 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).