From: Dave Jiang Date: Thu, 19 Apr 2018 20:39:43 +0000 (-0700) Subject: device-dax: allow MAP_SYNC to succeed X-Git-Tag: v4.19~1152^2~1 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=ef8423022324cf79bd1b41d8707c766461e7e555;p=platform%2Fkernel%2Flinux-rpi.git device-dax: allow MAP_SYNC to succeed MAP_SYNC is a nop for device-dax. Allow MAP_SYNC to succeed on device-dax to eliminate special casing between device-dax and fs-dax as to when the flag can be specified. Device-dax users already implicitly assume that they do not need to call fsync(), and this enables them to explicitly check for this capability. Cc: Fixes: b6fb293f2497 ("mm: Define MAP_SYNC and VM_SYNC flags") Signed-off-by: Dave Jiang Reviewed-by: Dan Williams Signed-off-by: Dan Williams --- diff --git a/drivers/dax/device.c b/drivers/dax/device.c index be86064..aff2c15 100644 --- a/drivers/dax/device.c +++ b/drivers/dax/device.c @@ -19,6 +19,7 @@ #include #include #include +#include #include "dax-private.h" #include "dax.h" @@ -540,6 +541,7 @@ static const struct file_operations dax_fops = { .release = dax_release, .get_unmapped_area = dax_get_unmapped_area, .mmap = dax_mmap, + .mmap_supported_flags = MAP_SYNC, }; static void dev_dax_release(struct device *dev)