Re: [PATCH v4 17/18] mm, fs, dax: dax_flush_dma, handle dma vs block-map-change collisions

To: Dan Williams <dan.j.williams@xxxxxxxxx>
Subject: Re: [PATCH v4 17/18] mm, fs, dax: dax_flush_dma, handle dma vs block-map-change collisions
From: Christoph Hellwig <hch@xxxxxx>
Date: Thu, 4 Jan 2018 09:31:29 +0100
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, jack@xxxxxxx, Matthew Wilcox <mawilcox@xxxxxxxxxxxxx>, Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-nvdimm@xxxxxxxxxxxx, Jeff Moyer <jmoyer@xxxxxxxxxx>, Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>, ross.zwisler@xxxxxxxxxxxxxxx, hch@xxxxxx
In-reply-to: <151407705124.38751.12934858054023659736.stgit@dwillia2-desk3.amr.corp.intel.com>
User-agent: Mutt/1.5.17 (2007-11-01)

Not pretty, but probably the best we can do for now..

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH v4 00/18] dax: fix dma vs truncate/hole-punch
  - From: Dan Williams
- [PATCH v4 17/18] mm, fs, dax: dax_flush_dma, handle dma vs block-map-change collisions
  - From: Dan Williams