From: Christoph Hellwig Subject: fix write synchronization for DAX Date: Tue, 10 Jan 2017 16:48:06 +0100 Message-ID: <1484063288-18255-1-git-send-email-hch@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org To: Jan Kara Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" List-Id: linux-ext4.vger.kernel.org While I've fixed both ext4 and XFS to not incorrectly allow parallel writers when mounting with -o dax ext4 still has this issue after the iomap conversion. Patch 1 fixes it, and patch 2 adds a lockdep assert to catch any new file systems copy and pasting from the direct I/O path.