From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([198.137.202.9]:52821 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932094AbcFVPnY (ORCPT ); Wed, 22 Jun 2016 11:43:24 -0400 From: Christoph Hellwig To: xfs@oss.sgi.com Cc: linux-nvdimm@ml01.01.org, linux-fsdevel@vger.kernel.org Subject: xfs: untangle the direct I/O and DAX path, fix DAX locking Date: Wed, 22 Jun 2016 17:27:08 +0200 Message-Id: <1466609236-23801-1-git-send-email-hch@lst.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: The last patch is what started the series: XFS currently uses the direct I/O locking strategy for DAX because DAX was overloaded onto the direct I/O path. For XFS this means that we only take a shared inode lock instead of the normal exclusive one for writes IFF they are properly aligned. While this is fine for O_DIRECT which requires explicit opt-in from the application it's not fine for DAX where we'll suddenly lose expected and required synchronization of the file system happens to use DAX undeneath. Patches 1-7 just untangle the code so that we can deal with DAX on it's own easily.