From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 3/6] libnvdimm/region: Register badblocks before namespaces
Date: Fri, 21 Jun 2019 00:56:24 +0000 [thread overview]
Message-ID: <76314eeafb50c74afbc77156f65cee2c0949478b.camel@intel.com> (raw)
In-Reply-To: <156029555941.419799.6074744061405561526.stgit@dwillia2-desk3.amr.corp.intel.com>
On Tue, 2019-06-11 at 16:25 -0700, Dan Williams wrote:
> Namespace activation expects to be able to reference region badblocks.
> The following warning sometimes triggers when asynchronous namespace
> activation races in front of the completion of namespace probing. Move
> all possible namespace probing after region badblocks initialization.
>
> Otherwise, lockdep sometimes catches the uninitialized state of the
> badblocks seqlock with stack trace signatures like:
>
> INFO: trying to register non-static key.
> pmem2: detected capacity change from 0 to 136365211648
> the code is fine but needs lockdep annotation.
> turning off the locking correctness validator.
> CPU: 9 PID: 358 Comm: kworker/u80:5 Tainted:
> G OE 5.2.0-rc4+ #3382
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0
> 02/06/2015
> Workqueue: events_unbound async_run_entry_fn
> Call Trace:
> dump_stack+0x85/0xc0
> pmem1.12: detected capacity change from 0 to 8589934592
> register_lock_class+0x56a/0x570
> ? check_object+0x140/0x270
> __lock_acquire+0x80/0x1710
> ? __mutex_lock+0x39d/0x910
> lock_acquire+0x9e/0x180
> ? nd_pfn_validate+0x28f/0x440 [libnvdimm]
> badblocks_check+0x93/0x1f0
> ? nd_pfn_validate+0x28f/0x440 [libnvdimm]
> nd_pfn_validate+0x28f/0x440 [libnvdimm]
> ? lockdep_hardirqs_on+0xf0/0x180
> nd_dax_probe+0x9a/0x120 [libnvdimm]
> nd_pmem_probe+0x6d/0x180 [nd_pmem]
> nvdimm_bus_probe+0x90/0x2c0 [libnvdimm]
>
> Fixes: 48af2f7e52f4 ("libnvdimm, pfn: during init, clear errors...")
> Cc: <stable@vger.kernel.org>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> drivers/nvdimm/region.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
This looks good to me,
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
>
> diff --git a/drivers/nvdimm/region.c b/drivers/nvdimm/region.c
> index ef46cc3a71ae..488c47ac4c4a 100644
> --- a/drivers/nvdimm/region.c
> +++ b/drivers/nvdimm/region.c
> @@ -34,17 +34,6 @@ static int nd_region_probe(struct device *dev)
> if (rc)
> return rc;
>
> - rc = nd_region_register_namespaces(nd_region, &err);
> - if (rc < 0)
> - return rc;
> -
> - ndrd = dev_get_drvdata(dev);
> - ndrd->ns_active = rc;
> - ndrd->ns_count = rc + err;
> -
> - if (rc && err && rc == err)
> - return -ENODEV;
> -
> if (is_nd_pmem(&nd_region->dev)) {
> struct resource ndr_res;
>
> @@ -60,6 +49,17 @@ static int nd_region_probe(struct device *dev)
> nvdimm_badblocks_populate(nd_region, &nd_region->bb,
> &ndr_res);
> }
>
> + rc = nd_region_register_namespaces(nd_region, &err);
> + if (rc < 0)
> + return rc;
> +
> + ndrd = dev_get_drvdata(dev);
> + ndrd->ns_active = rc;
> + ndrd->ns_count = rc + err;
> +
> + if (rc && err && rc == err)
> + return -ENODEV;
> +
> nd_region->btt_seed = nd_btt_create(nd_region);
> nd_region->pfn_seed = nd_pfn_create(nd_region);
> nd_region->dax_seed = nd_dax_create(nd_region);
>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2019-06-21 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 23:25 [PATCH 0/6] libnvdimm: Fix async operations and locking Dan Williams
2019-06-11 23:25 ` [PATCH 1/6] drivers/base: Introduce kill_device() Dan Williams
2019-06-11 23:25 ` [PATCH 2/6] libnvdimm/bus: Prevent duplicate device_unregister() calls Dan Williams
2019-06-11 23:25 ` [PATCH 3/6] libnvdimm/region: Register badblocks before namespaces Dan Williams
2019-06-21 0:56 ` Verma, Vishal L [this message]
2019-06-11 23:26 ` [PATCH 4/6] libnvdimm/bus: Stop holding nvdimm_bus_list_mutex over __nd_ioctl() Dan Williams
2019-06-11 23:26 ` [PATCH 5/6] libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock Dan Williams
2019-06-11 23:26 ` [PATCH 6/6] driver-core, libnvdimm: Let device subsystems add local lockdep coverage Dan Williams
2019-06-19 22:21 ` Dan Williams
2019-06-20 6:34 ` Greg Kroah-Hartman
2019-06-18 22:10 ` [PATCH 0/6] libnvdimm: Fix async operations and locking Jane Chu
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=76314eeafb50c74afbc77156f65cee2c0949478b.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.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