From: Vishal Verma <vishal.l.verma@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Tony Luck <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] nfit, libnvdimm: allow an ARS scrub to be triggered on demand
Date: Thu, 21 Jul 2016 12:07:44 -0600 [thread overview]
Message-ID: <20160721180742.GG12960@omniknight.lm.intel.com> (raw)
In-Reply-To: <CAPcyv4jpmnGf6e_Akot4fuvckVZQAAnQmSLs8Ytd3sqHLj6UrQ@mail.gmail.com>
On 07/21, Dan Williams wrote:
> On Wed, Jul 20, 2016 at 6:50 PM, Vishal Verma <vishal.l.verma@intel.com> wrote:
> > Normally, an ARS (Address Range Scrub) only happens at
> > boot/initialization time. There can however arise situations where a
> > bus-wide rescan is needed - notably, in the case of discovering a latent
> > media error, we should do a full rescan to figure out what other sectors
> > are bad, and thus potentially avoid triggering an mce on them in the
> > future. Also provide a sysfs trigger to start a bus-wide scrub.
> >
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > Cc: <linux-acpi@vger.kernel.org>
> > Cc: <linux-nvdimm@lists.01.org>
> > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> > ---
> > drivers/acpi/nfit.c | 123 +++++++++++++++++++++++++++++++++------
> > drivers/acpi/nfit.h | 4 +-
> > drivers/nvdimm/core.c | 7 +++
> > include/linux/libnvdimm.h | 1 +
> > tools/testing/nvdimm/test/nfit.c | 16 +++++
> > 5 files changed, 131 insertions(+), 20 deletions(-)
> >
>
> Looks good, just a couple nits:
>
> [..]
> > @@ -2138,7 +2172,7 @@ static void acpi_nfit_async_scrub(struct acpi_nfit_desc *acpi_desc,
> > unsigned int tmo = scrub_timeout;
> > int rc;
> >
> > - if (nfit_spa->ars_done || !nfit_spa->nd_region)
> > + if (!(nfit_spa->ars_required && nfit_spa->nd_region))
> > return;
>
> Why is nd_region part of this check? Can't this just be:
>
> if (!nfit_spa->ars_requested)
> return;
>
> [..]
This was there previously too - I think we should always have nd_region
when we get here, and if we don't that's a kernel bug. So we could just
BUG_ON if that happens.. If we don't have a valid nd_region, it will
cause an oops when we go to call nvdimm_region_notify..
I'll change it to a BUG_ON.
> >
> > +static struct acpi_nfit_desc *acpi_nfit_desc_alloc_register(struct device *dev)
> > +{
> > + struct acpi_nfit_desc *acpi_desc;
> > + struct kernfs_node *nfit;
> > + struct device *bus_dev;
> > +
> > + acpi_desc = devm_kzalloc(dev, sizeof(*acpi_desc), GFP_KERNEL);
> > + if (!acpi_desc)
> > + return ERR_PTR(-ENOMEM);
> > +
> > + acpi_nfit_desc_init(acpi_desc, dev);
> > +
> > + acpi_desc->nvdimm_bus = nvdimm_bus_register(dev, &acpi_desc->nd_desc);
> > + if (!acpi_desc->nvdimm_bus)
> > + return ERR_PTR(-ENOMEM);
> > +
> > + bus_dev = to_nvdimm_bus_dev(acpi_desc->nvdimm_bus);
> > + nfit = sysfs_get_dirent(bus_dev->kobj.sd, "nfit");
> > + if (!nfit) {
> > + dev_err(dev, "sysfs_get_dirent 'nfit' failed\n");
> > + return ERR_PTR(-ENODEV);
> > + }
> > + acpi_desc->scrub_count_state = sysfs_get_dirent(nfit, "scrub");
>
> Missing sysfs_put(nfit) here?
Yes, good catch! I'll fixup.
>
> > + if (!acpi_desc->scrub_count_state) {
> > + dev_err(dev, "sysfs_get_dirent 'scrub' failed\n");
> > + return ERR_PTR(-ENODEV);
> > + }
next prev parent reply other threads:[~2016-07-21 18:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 1:50 [PATCH v2 0/3] ARS rescanning triggered by latent errors or userspace Vishal Verma
2016-07-21 1:50 ` [PATCH v2 1/3] pmem: clarify a debug print in pmem_clear_poison Vishal Verma
2016-07-21 1:50 ` [PATCH v2 2/3] nfit, libnvdimm: allow an ARS scrub to be triggered on demand Vishal Verma
2016-07-21 15:56 ` Dan Williams
2016-07-21 18:07 ` Vishal Verma [this message]
2016-07-21 19:40 ` Linda Knippers
2016-07-21 19:46 ` Dan Williams
2016-07-21 19:55 ` Linda Knippers
2016-07-21 19:59 ` Dan Williams
2016-07-21 1:50 ` [PATCH v2 3/3] nfit: do an ARS scrub on hitting a latent media error Vishal Verma
2016-07-21 20:54 ` Linda Knippers
2016-07-21 21:10 ` Vishal Verma
2016-07-21 21:25 ` Linda Knippers
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=20160721180742.GG12960@omniknight.lm.intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).