All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Saldivar, Maurice A." <maurice.a.saldivar@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: ndctl-58 causing kernel panic w/ latest kernel
Date: Mon, 18 Sep 2017 14:02:12 +0000	[thread overview]
Message-ID: <1505742903.3864.2.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4hMdFrbu0qfCHJGe4OS7E22evj5tPPYY1pE-uQ-Q9vo_g@mail.gmail.com>

On Fri, 2017-09-15 at 17:16 -0700, Dan Williams wrote:
> On Fri, Sep 15, 2017 at 2:41 PM, Saldivar, Maurice A.
> <maurice.a.saldivar@hpe.com> wrote:
> > 
> > Testing ndctl-58 on our NVDIMM-Ns with the latest kernel (4.13.2)
> > causes a panic when configuring a pmem device from raw to sector
> > mode.
> > 
> > ndctl create-namespace -f -e namespace0.0 -m sector
> > 
> > I was not able to reproduce this issue using ndctl-57. Below is the
> > stack trace from configuring a pmem device from raw to sector mode.
> > 
> > BUG: unable to handle kernel NULL pointer dereference at
> > 0000000000000028
> > IP: holder_class_store+0x253/0x2b0 [libnvdimm]
> Can you translate this to a line number? Try the following, and send
> the output:
> 
> $ gdb drivers/nvdimm/libnvdimm.ko
> (gdb) li *(holder_class_store+0x253)


Yup, I ran the command and got the following output:
 
Reading symbols from
/usr/lib/modules/4.13.2/kernel/drivers/nvdimm/libnvdimm.ko...done.
(gdb) li *(holder_class_store+0x253)
0x7773 is in holder_class_store (drivers/nvdimm/namespace_devs.c:1420).
1415		for (i = 0; i < nd_region->ndr_mappings; i++) {
1416			struct nd_mapping *nd_mapping = &nd_region-
>mapping[i];
1417			struct nvdimm_drvdata *ndd =
to_ndd(nd_mapping);
1418			struct nd_namespace_index *nsindex;
1419	
1420			nsindex = to_namespace_index(ndd, ndd-
>ns_current);
1421			if (nsindex == NULL)
1422				loop_bitmask |= 1;
1423			else {
1424				/* check whether existing labels
are v1.1 or v1.2 */
(gdb) 

Sincerely,
Maurice  
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

      reply	other threads:[~2017-09-18 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 21:41 ndctl-58 causing kernel panic w/ latest kernel Saldivar, Maurice A.
2017-09-16  0:16 ` Dan Williams
2017-09-18 14:02   ` Saldivar, Maurice A. [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=1505742903.3864.2.camel@hpe.com \
    --to=maurice.a.saldivar@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.