Skip to content
Commit 273752c9 authored by Vivek Goyal's avatar Vivek Goyal Committed by Mike Snitzer
Browse files

dm, dax: Make sure dm_dax_flush() is called if device supports it



Currently dm_dax_flush() is not being called, even if underlying dax
device supports write cache, because DAXDEV_WRITE_CACHE is not being
propagated up to the DM dax device.

If the underlying dax device supports write cache, set
DAXDEV_WRITE_CACHE on the DM dax device.  This will cause dm_dax_flush()
to be called.

Fixes: abebfbe2 ("dm: add ->flush() dax operation support")
Signed-off-by: default avatarVivek Goyal <vgoyal@redhat.com>
Acked-by: default avatarDan Williams <dan.j.williams@intel.com>
Signed-off-by: default avatarMike Snitzer <snitzer@redhat.com>
parent 34c96507
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment