On Tue, Sep 27, 2016 at 06:43:34PM +0200, Jan Kara wrote: > Currently invalidate_inode_pages2_range() and invalidate_mapping_pages() > just delete all exceptional radix tree entries they find. For DAX this > is not desirable as we track cache dirtiness in these entries and when > they are evicted, we may not flush caches although it is necessary. This > can for example manifest when we write to the same block both via mmap > and via write(2) (to different offsets) and fsync(2) then does not > properly flush CPU caches when modification via write(2) was the last > one.
Can you come up with an xfstests test case for these data loss cases? _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
