device-dax: fail all private mapping attempts
The device-dax implementation originally tried to be tricky and allow private read-only mappings, but in the process allowed writable MAP_PRIVATE + MAP_NORESERVE mappings. For simplicity and predictability just fail all private mapping attempts since device-dax memory is statically allocated and will never support overcommit. Cc: <stable@vger.kernel.org> Cc: Dave Hansen <dave.hansen@linux.intel.com> Fixes: dee41079 ("/dev/dax, core: file operations and dax-mmap") Reported-by:Pawel Lebioda <pawel.lebioda@intel.com> Signed-off-by:
Dan Williams <dan.j.williams@intel.com>
parent
6a84fb4b
Please register or sign in to comment