Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754305AbdIFCMl (ORCPT ); Tue, 5 Sep 2017 22:12:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:53700 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754229AbdIFCMi (ORCPT ); Tue, 5 Sep 2017 22:12:38 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 0C81781DE0 Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=esandeen@redhat.com Reply-To: sandeen@redhat.com Subject: Re: [PATCH 0/9] add ext4 per-inode DAX flag To: Ross Zwisler , Andrew Morton , linux-kernel@vger.kernel.org Cc: "Darrick J. Wong" , "Theodore Ts'o" , Andreas Dilger , Christoph Hellwig , Dan Williams , Dave Chinner , Jan Kara , linux-ext4@vger.kernel.org, linux-nvdimm@lists.01.org, linux-xfs@vger.kernel.org References: <20170905223541.20594-1-ross.zwisler@linux.intel.com> From: Eric Sandeen Message-ID: Date: Tue, 5 Sep 2017 21:12:35 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20170905223541.20594-1-ross.zwisler@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Wed, 06 Sep 2017 02:12:38 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1848 Lines: 44 On 9/5/17 5:35 PM, Ross Zwisler wrote: > The original intent of this series was to add a per-inode DAX flag to ext4 > so that it would be consistent with XFS. In my travels I found and fixed > several related issues in both ext4 and XFS. Hi Ross - hch had a lot of reasons to nuke the dax flag from orbit, and we just /disabled/ it in xfs due to its habit of crashing the kernel... so a couple questions: 1) does this series pass hch's "test the per-inode DAX flag" fstest? 2) do we have an agreement that we need this flag at all, or is this just a parity item because xfs has^whad a per-inode flag? Thanks, -Eric > I'm not fully happy with the ways that ext4 DAX interacts with conflicting > features (journaling, inline data and encryption). My goal with this > series was to make all these interactions as consistent as possilble, and > of course to make them safe. If anyone has ideas for improvements, I'm > very open. > > Ross Zwisler (9): > ext4: remove duplicate extended attributes defs > xfs: always use DAX if mount option is used > xfs: validate bdev support for DAX inode flag > ext4: add ext4_should_use_dax() > ext4: ext4_change_inode_journal_flag error handling > ext4: safely transition S_DAX on journaling changes > ext4: prevent data corruption with inline data + DAX > ext4: add sanity check for encryption + DAX > ext4: add per-inode DAX flag > > fs/ext4/ext4.h | 47 ++++++--------------------------------------- > fs/ext4/ext4_jbd2.h | 16 ++++++++++++++++ > fs/ext4/inline.c | 10 ---------- > fs/ext4/inode.c | 45 ++++++++++++++++++++++++------------------- > fs/ext4/ioctl.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++-- > fs/ext4/super.c | 8 ++++++++ > fs/xfs/xfs_ioctl.c | 14 +++++++++++--- > 7 files changed, 119 insertions(+), 76 deletions(-) >