diff options
author | Dan Williams <dan.j.williams@intel.com> | 2017-11-13 16:38:44 -0800 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2017-11-13 16:38:44 -0800 |
commit | aaa422c4c3f6ee958ea9d6c9260ac40f90a3f4e9 (patch) | |
tree | 64ce62bb891f903a5c504a2700823cbd60bb877c /drivers/dax | |
parent | a39e596baa07cb1dc19c2ead14c9fd2a30f22352 (diff) |
fs, dax: unify IOMAP_F_DIRTY read vs write handling policy in the dax core
While reviewing whether MAP_SYNC should strengthen its current guarantee
of syncing writes from the initiating process to also include
third-party readers observing dirty metadata, Dave pointed out that the
check of IOMAP_WRITE is misplaced.
The policy of what to with IOMAP_F_DIRTY should be separated from the
generic filesystem mechanism of reporting dirty metadata. Move this
policy to the fs-dax core to simplify the per-filesystem iomap handlers,
and further centralize code that implements the MAP_SYNC policy. This
otherwise should not change behavior, it just makes it easier to change
behavior in the future.
Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
Reported-by: Dave Chinner <david@fromorbit.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/dax')
0 files changed, 0 insertions, 0 deletions