Vivek Goyal 4e4ced9379 dax: Move mandatory ->zero_page_range() check in alloc_dax() ... zero_page_range() dax operation is mandatory for dax devices. Right now that check happens in dax_zero_page_range() function. Dan thinks that's too late and its better to do the check earlier in alloc_dax(). I also modified alloc_dax() to return pointer with error code in it in case of failure. Right now it returns NULL and caller assumes failure happened due to -ENOMEM. But with this ->zero_page_range() check, I need to return -EINVAL instead. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Link: https://lore.kernel.org/r/20200401161125.GB9398@redhat.com Signed-off-by: Dan Williams <dan.j.williams@intel.com>		2020-04-02 19:15:03 -07:00
..
pmem	libnvdimm/namespace: Differentiate between probe mapping and runtime mapping	2019-11-14 19:08:47 -08:00
bus.c	dax: Move mandatory ->zero_page_range() check in alloc_dax()	2020-04-02 19:15:03 -07:00
bus.h	dax: Fix alloc_dax_region() compile warning	2019-11-07 15:44:47 +01:00
dax-private.h	dax: Fix alloc_dax_region() compile warning	2019-11-07 15:44:47 +01:00
device.c	device-dax: use the dev_pagemap internal refcount	2019-07-02 14:32:44 -03:00
hmem.c	device-dax: Add a driver for "hmem" devices	2019-11-07 15:45:00 +01:00
Kconfig	device-dax: Add a driver for "hmem" devices	2019-11-07 15:45:00 +01:00
kmem.c	device-dax: "Hotremove" persistent memory that is used like normal RAM	2019-07-16 19:23:24 -07:00
Makefile	device-dax: Add a driver for "hmem" devices	2019-11-07 15:45:00 +01:00
super.c	dax: Move mandatory ->zero_page_range() check in alloc_dax()	2020-04-02 19:15:03 -07:00