Received: by 2002:a25:2c96:0:0:0:0:0 with SMTP id s144csp858010ybs; Mon, 25 May 2020 00:31:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzqWdaGySUaIg6XnF7E/7EyY3OHH70D3PEFy7qoLxmok4+SZwtgPsXeISq4TbnKz1tdz533 X-Received: by 2002:a05:6402:22d1:: with SMTP id dm17mr13420337edb.299.1590391919192; Mon, 25 May 2020 00:31:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590391919; cv=none; d=google.com; s=arc-20160816; b=rfznpYDuIzQrr6wuMYRJykWLx25VtP7i99HRJsDAJUd6tTRVglcQm4uroBXpj/gj5g oMaX/8UaU1+QNo3vqgIaTITiZztbY4KNwJNzrofVx5/Dcb/0DAtNS6qm6mvwCf4NN5Wz MKK36ZB1bVOg+w0HVwUQMFWiGWDWqaXFXk06UrGurSz527fefvCrAxEZWUFRa5RhZcm9 uBZ8LFbR1xegO621D6ijfwDXxOJBQ5LzNgYtE5wiQLmcDNuNqpizeq0qp9qjnhQxkWMW 05T2cNafP2+QWRNU06rSUzjOZGiK+ebERGTDUQr/7m0gvdcL4/GpaI7r7X1rmqYvyJKI JbeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Pb6aAXAv3uUX3ctWpvrBJ5OtzsT3b4cRtdFNHptvgMA=; b=Lo98g0K89qQhO7sbIJA/EV4X+4gHJbS5kulixqLj8JYh6Yi1ensQT9Vw211ERGd/at eVBlgwHSD1h4CIw3AMgM8ufr4cvDFzwrfW5iNE+9RXGeYnfkBsAZOvu47QfIbPS2cL48 xrPTcbUyPhMzTy7pWEc6g5BrhWSRd1NfI1/QPlCgYoMNbDPS39rDmaAoRo4MekDVGKXI StzRBnp92hSoOhiBGpLMhgDJhhzp0LyipGdGLGJUREB2lzC2q78JZBreTXl4Eelo/OKm cFLfVTaMs4l3vtEy+4S1l6ZEWg5yzimSfNFU8YgD2C9zfPJatRARMaXMyFtlBHND9jCb 7InA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d8si8603044ejk.317.2020.05.25.00.31.29; Mon, 25 May 2020 00:31:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389105AbgEYH2r (ORCPT + 99 others); Mon, 25 May 2020 03:28:47 -0400 Received: from mx2.suse.de ([195.135.220.15]:58302 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388948AbgEYH2r (ORCPT ); Mon, 25 May 2020 03:28:47 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 56897B083; Mon, 25 May 2020 07:28:48 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id EF42C1E1270; Mon, 25 May 2020 09:28:44 +0200 (CEST) Date: Mon, 25 May 2020 09:28:44 +0200 From: Jan Kara To: Ira Weiny Cc: Jan Kara , linux-ext4@vger.kernel.org, Andreas Dilger , "Theodore Y. Ts'o" , Eric Biggers , Al Viro , Dan Williams , Dave Chinner , Christoph Hellwig , Jeff Moyer , "Darrick J. Wong" , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V4 7/8] fs/ext4: Introduce DAX inode flag Message-ID: <20200525072844.GH14199@quack2.suse.cz> References: <20200521191313.261929-1-ira.weiny@intel.com> <20200521191313.261929-8-ira.weiny@intel.com> <20200522114848.GC14199@quack2.suse.cz> <20200525043910.GA319107@iweiny-DESK2.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200525043910.GA319107@iweiny-DESK2.sc.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Sun 24-05-20 21:39:10, Ira Weiny wrote: > On Fri, May 22, 2020 at 01:48:48PM +0200, Jan Kara wrote: > > And then we should check conflicts with the journal flag as well, as I > > mentioned in reply to the first patch. There it is more complicated by the > > fact that we should disallow setting of both EXT4_INODE_DAX_FL and > > EXT4_JOURNAL_DATA_FL at the same time so the checks will be somewhat more > > complicated. > > I'm confused by jflag. Why is EXT4_JOURNAL_DATA_FL stored in jflag? It isn't just EXT4_JOURNAL_DATA_FL. It is: jflag = flags & EXT4_JOURNAL_DATA_FL; so it is EXT4_JOURNAL_DATA_FL if it should be set by the current ioctl and 0 otherwise. But I agree that since we mostly do (jflag ^ oldflags) & EXT4_JOURNAL_DATA_FL jflags is mostly useless as we could do just (flags ^ oldflags) & EXT4_JOURNAL_DATA_FL I guess it's mostly a relict from the past... Honza -- Jan Kara SUSE Labs, CR