From: Jason Wang <jasowang@redhat.com>
To: dan.j.williams@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, ira.weiny@intel.com,
nvdimm@lists.linux.dev, mst@redhat.com, jasowang@redhat.com
Subject: [PATCH 2/2] virtio_pmem: set device ready in probe()
Date: Mon, 20 Jun 2022 16:15:19 +0800 [thread overview]
Message-ID: <20220620081519.1494-2-jasowang@redhat.com> (raw)
In-Reply-To: <20220620081519.1494-1-jasowang@redhat.com>
The NVDIMM region could be available before the virtio_device_ready()
that is called by virtio_dev_probe(). This means the driver tries to
use device before DRIVER_OK which violates the spec, fixing this by
set device ready before the nvdimm_pmem_region_create().
Note that this means the virtio_pmem_host_ack() could be triggered
before the creation of the nd region, this is safe since the
virtio_pmem_host_ack() since pmem_lock has been initialized and we
check if we've added any buffer before trying to proceed.
Fixes 6e84200c0a29 ("virtio-pmem: Add virtio pmem driver")
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
drivers/nvdimm/virtio_pmem.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/drivers/nvdimm/virtio_pmem.c b/drivers/nvdimm/virtio_pmem.c
index 48f8327d0431..173f2f5adaea 100644
--- a/drivers/nvdimm/virtio_pmem.c
+++ b/drivers/nvdimm/virtio_pmem.c
@@ -84,6 +84,17 @@ static int virtio_pmem_probe(struct virtio_device *vdev)
ndr_desc.provider_data = vdev;
set_bit(ND_REGION_PAGEMAP, &ndr_desc.flags);
set_bit(ND_REGION_ASYNC, &ndr_desc.flags);
+ /*
+ * The NVDIMM region could be available before the
+ * virtio_device_ready() that is called by
+ * virtio_dev_probe(), so we set device ready here.
+ *
+ * The callback - virtio_pmem_host_ack() is safe to be called
+ * before the nvdimm_pmem_region_create() since the pmem_lock
+ * has been initialized and legality of a used buffer is
+ * validated before moving forward.
+ */
+ virtio_device_ready(vdev);
nd_region = nvdimm_pmem_region_create(vpmem->nvdimm_bus, &ndr_desc);
if (!nd_region) {
dev_err(&vdev->dev, "failed to create nvdimm region\n");
@@ -92,6 +103,7 @@ static int virtio_pmem_probe(struct virtio_device *vdev)
}
return 0;
out_nd:
+ virtio_reset_device(vdev);
nvdimm_bus_unregister(vpmem->nvdimm_bus);
out_vq:
vdev->config->del_vqs(vdev);
--
2.25.1
next prev parent reply other threads:[~2022-06-20 8:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 8:15 [PATCH 1/2] virtio_pmem: initialize provider_data through nd_region_desc Jason Wang
2022-06-20 8:15 ` Jason Wang [this message]
2022-06-20 8:32 ` [PATCH 2/2] virtio_pmem: set device ready in probe() Michael S. Tsirkin
2022-06-20 8:39 ` Jason Wang
2022-06-20 8:53 ` Michael S. Tsirkin
2022-06-21 12:34 ` Pankaj Gupta
2022-06-21 22:38 ` Dan Williams
2022-06-22 3:34 ` Jason Wang
2022-06-22 6:29 ` Michael S. Tsirkin
2022-06-22 7:24 ` Jason Wang
2022-06-22 12:31 ` Michael S. Tsirkin
2022-06-23 1:29 ` Jason Wang
2022-06-23 3:57 ` Jason Wang
2022-06-24 6:44 ` Michael S. Tsirkin
2022-06-20 8:36 ` [PATCH 1/2] virtio_pmem: initialize provider_data through nd_region_desc Michael S. Tsirkin
2022-06-20 8:36 ` Jason Wang
2022-06-21 12:44 ` Pankaj Gupta
2022-06-22 3:35 ` Jason Wang
2022-06-21 22:34 ` Dan Williams
2022-06-22 3:22 ` Jason Wang
2022-06-24 6:46 ` Michael S. Tsirkin
2022-06-27 2:31 ` Jason Wang
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=20220620081519.1494-2-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=mst@redhat.com \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.com \
/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