From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>
Subject: Re: [PATCH] libnvdimm: Fix nvdimm_probe error on NVDIMM-N
Date: Tue, 16 Aug 2016 15:05:48 +0000 [thread overview]
Message-ID: <1471359928.32015.57.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4gPQcqHQHSKpF1cqK22cppyHxNf7swE3QcssY5tdE3evQ@mail.gmail.com>
On Mon, 2016-08-15 at 14:20 -0700, Dan Williams wrote:
> On Mon, Aug 15, 2016 at 10:52 AM, Toshi Kani <toshi.kani@hpe.com>
> wrote:
> >
> > 'ndctl list --buses --dimms' does not list any NVDIMM-Ns since
> > they are considered as idle. ndctl checks if any driver is
> > attached to nmem device. nvdimm_probe() always fails in
> > nvdimm_init_nsarea() since NVDIMM-Ns do not implement optinal
> > ND_CMD_GET_CONFIG_DATA command.
> >
> > Change nvdimm_probe() to accept the case that the CONFIG_DATA
> > command is not implemented for NVDIMM-Ns. The driver attaches
> > without ndd, which keeps it no-op to the device.
> >
> > Reported-by: Brian Boylston <brian.boylston@hpe.com>
> > Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > ---
> > drivers/nvdimm/dimm.c | 10 ++++++++++
> > drivers/nvdimm/dimm_devs.c | 27 ++++++++++++++++-----------
> > drivers/nvdimm/nd.h | 1 +
> > 3 files changed, 27 insertions(+), 11 deletions(-)
>
> This fails the ndctl unit test suite, see below plus some other
> cleanups...
Sorry, I had overlooked about this test suite... I built it to run the
test and was able to reproduce the failures.
> >
> > diff --git a/drivers/nvdimm/dimm.c b/drivers/nvdimm/dimm.c
> > index 71d12bb..07e09c2 100644
> > --- a/drivers/nvdimm/dimm.c
> > +++ b/drivers/nvdimm/dimm.c
> > @@ -26,6 +26,13 @@ static int nvdimm_probe(struct device *dev)
> > struct nvdimm_drvdata *ndd;
> > int rc;
> >
> > + rc = nvdimm_check_config_data(dev);
> > + if (rc == -ENOENT)
> > + /* not required for non-aliased nvdimm, ex. NVDIMM-
> > N */
> > + return 0;
> > + else
> > + return rc;
> > +
>
> Change usage of ENOENT to ENOTTY throughout...
Will do.
> >
> > ndd = kzalloc(sizeof(*ndd), GFP_KERNEL);
> > if (!ndd)
> > return -ENOMEM;
> > @@ -72,6 +79,9 @@ static int nvdimm_remove(struct device *dev)
> > {
> > struct nvdimm_drvdata *ndd = dev_get_drvdata(dev);
> >
> > + if (!ndd)
> > + return 0;
> > +
> > nvdimm_bus_lock(dev);
> > dev_set_drvdata(dev, NULL);
> > nvdimm_bus_unlock(dev);
> > diff --git a/drivers/nvdimm/dimm_devs.c
> > b/drivers/nvdimm/dimm_devs.c
> > index d9bba5e..fee82d3 100644
> > --- a/drivers/nvdimm/dimm_devs.c
> > +++ b/drivers/nvdimm/dimm_devs.c
> > @@ -28,28 +28,33 @@ static DEFINE_IDA(dimm_ida);
> > * Retrieve bus and dimm handle and return if this bus supports
> > * get_config_data commands
> > */
> > -static int __validate_dimm(struct nvdimm_drvdata *ndd)
> > +int nvdimm_check_config_data(struct device *dev)
> > {
> > - struct nvdimm *nvdimm;
> > -
> > - if (!ndd)
> > - return -EINVAL;
> > -
> > - nvdimm = to_nvdimm(ndd->dev);
> > + struct nvdimm *nvdimm = to_nvdimm(dev);
> >
> > if (!nvdimm->cmd_mask)
> > - return -ENXIO;
> > + goto err;
> > if (!test_bit(ND_CMD_GET_CONFIG_DATA, &nvdimm->cmd_mask))
> > - return -ENXIO;
> > + goto err;
> >
> > return 0;
> > +
> > + err:
> > + if (nvdimm->flags & NDD_ALIASING)
> > + return -ENXIO;
> > + else
> > + return -ENOENT;
>
>
> Let's not use "goto" since there is nothing to unwind.
Got it.
> >
> > }
> >
> > static int validate_dimm(struct nvdimm_drvdata *ndd)
> > {
> > - int rc = __validate_dimm(ndd);
> > + int rc;
> >
> > - if (rc && ndd)
> > + if (!ndd)
> > + return -EINVAL;
>
> Since we've called nvdimm_check_config_data() before allocating ndd
> it will always be NULL causing DIMMs with label areas to fail init.
I am still puzzled at the moment, but will look into the issue.
Thanks!
-Toshi
prev parent reply other threads:[~2016-08-16 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 17:52 [PATCH] libnvdimm: Fix nvdimm_probe error on NVDIMM-N Toshi Kani
2016-08-15 21:20 ` Dan Williams
2016-08-16 15:05 ` Kani, Toshimitsu [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=1471359928.32015.57.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.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