From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Mulumudi, Abhilash Kumar" <m.abhilash-kumar@hpe.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"brian.starkey@arm.com" <brian.starkey@arm.com>
Subject: RE: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()
Date: Wed, 24 Aug 2016 01:29:56 +0000 [thread overview]
Message-ID: <CS1PR84MB0005F40F71804F3988DD23CB82EA0@CS1PR84MB0005.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAPcyv4gJtTj8chX_eTNhs1PJ=D3X7USuDXwFSWSEZt1cUAXpUw@mail.gmail.com>
> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu <toshi.kani@hpe.com>
> wrote:
> > On Tue, 2016-08-23 at 15:32 -0700, Dan Williams wrote:
> >> On Tue, Aug 23, 2016 at 11:43 AM, Toshi Kani <toshi.kani@hpe.com>
> >> wrote:
> > :
> >> I'm not sure about this fix. The point of honoring
> >> vmem_altmap_offset() is because a portion of the resource that is
> >> passed to devm_memremap_pages() also contains the metadata info
> block
> >> for the device. The offset says "use everything past this point for
> >> pages". This may work for avoiding a crash, but it may corrupt info
> >> block metadata in the process. Can you provide more information
> >> about the failing scenario to be sure that we are not triggering a
> >> fault on an address that is not meant to have a page mapping? I.e.
> >> what is the host physical address of the page that caused this fault,
> >> and is it valid?
> >
> > The fault address in question was the 2nd page of an NVDIMM range. I
> > assumed this fault address was valid and needed to be handled. Here is
> > some info about the base and patched cases. Let me know if you need
> > more info.
> >
> > Base
> > ====
> >
> > The following NVDIMM range was set to /dev/dax.
>
> With ndctl create-namespace or manually via sysfs? Specifically I'm
> looking for what the 'align' attribute was set to when the
> configuration was established. Can you provide a dump of the sysfs
> attributes for the /dev/dax parent device?
I used the ndctl command below.
ndctl create-namespace -f -e namespace0.0 -m dax
Here is additional info from my note for the base case.
p {struct dev_pagemap} 0xffff88046d0453f0
$3 = {
altmap = 0xffff88046d045410,
res = 0xffff88046d0453a8,
ref = 0xffff88046d0452f0,
dev = 0xffff880464790410
}
crash> p {struct vmem_altmap} 0xffff88046d045410
$6 = {
base_pfn = 0x480000,
reserve = 0x2, // PHYS_PFN(SZ_8K)
free = 0x101fe,
align = 0x1fe,
alloc = 0x10000
}
crash> p {struct resource} 0xffff88046d0453a8
$4 = {
start = 0x480000000,
end = 0x87fffffff,
name = 0xffff880c7da5d4a8 "region0",
flags = 0x200,
desc = 0x0,
parent = 0x0,
sibling = 0x0,
child = 0x0
}
crash> p {struct percpu_ref} 0xffff88046d0452f0
$7 = {
count = {
counter = 0x8000000000000001
},
percpu_count_ptr = 0x60f380403a98,
release = 0xffffffffa008a0a0,
confirm_switch = 0x0,
force_atomic = 0x0,
rcu = {
next = 0x0,
func = 0x0
}
}
Thanks,
-Toshi
next prev parent reply other threads:[~2016-08-24 3:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:43 Toshi Kani
2016-08-23 20:42 ` Andrew Morton
2016-08-23 21:25 ` Kani, Toshimitsu
2016-08-23 22:32 ` Dan Williams
2016-08-23 23:47 ` Kani, Toshimitsu
2016-08-24 0:34 ` Dan Williams
2016-08-24 1:29 ` Kani, Toshimitsu [this message]
2016-08-24 2:53 ` Dan Williams
2016-08-24 3:58 ` Dan Williams
2016-08-24 4:28 ` Kani, Toshimitsu
2016-08-24 4:48 ` Dan Williams
2016-08-24 14:40 ` Kani, Toshimitsu
2016-08-24 14:55 ` Dan Williams
2016-08-24 5:48 ` Dan Williams
2016-08-24 15:21 ` Kani, Toshimitsu
2016-08-24 1:00 ` Dan Williams
2016-08-24 1:38 ` Kani, Toshimitsu
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=CS1PR84MB0005F40F71804F3988DD23CB82EA0@CS1PR84MB0005.NAMPRD84.PROD.OUTLOOK.COM \
--to=toshi.kani@hpe.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=brian.starkey@arm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=m.abhilash-kumar@hpe.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
all inboxes | Powered by JetHome®