summaryrefslogtreecommitdiffstats
path: root/drivers/dax
diff options
context:
space:
mode:
authorAneesh Kumar K.V <aneesh.kumar@linux.ibm.com>2019-11-01 08:57:28 +0530
committerDan Williams <dan.j.williams@intel.com>2019-11-14 19:08:47 -0800
commitc1f45d86a522d568aef541dbbc066ccac262b4c3 (patch)
tree6e8b9067b3f40f98a0a0e794c0f882bfc0158b8f /drivers/dax
parent2f4741497c9d5151c6bde0edb6faf34fc3859b80 (diff)
downloadblackbird-op-linux-c1f45d86a522d568aef541dbbc066ccac262b4c3.tar.gz
blackbird-op-linux-c1f45d86a522d568aef541dbbc066ccac262b4c3.zip
libnvdimm/pfn_dev: Don't clear device memmap area during generic namespace probe
nvdimm core use nd_pfn_validate when looking for devdax or fsdax namespace. In this case device resources are allocated against nd_namespace_io dev. In-order to allow remap of range in nd_pfn_clear_memmap_error(), move the device memmap area clearing while initializing pfn namespace. With this device resource are allocated against nd_pfn and we can use nd_pfn->dev for remapping. This also avoids calling nd_pfn_clear_mmap_errors twice. Once while probing the namespace and second while initializing a pfn namespace. Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> Link: https://lore.kernel.org/r/20191101032728.113001-1-aneesh.kumar@linux.ibm.com Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/dax')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud