From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f50.google.com ([209.85.218.50]:35310 "EHLO mail-oi0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S971156AbeCSUKy (ORCPT ); Mon, 19 Mar 2018 16:10:54 -0400 Received: by mail-oi0-f50.google.com with SMTP id a189so8438412oii.2 for ; Mon, 19 Mar 2018 13:10:54 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180319194513.GA3160@lst.de> References: <152112908134.24669.10222746224538377035.stgit@dwillia2-desk3.amr.corp.intel.com> <152112914933.24669.5543317105428477772.stgit@dwillia2-desk3.amr.corp.intel.com> <20180319173345.GF1757@magnolia> <20180319194513.GA3160@lst.de> From: Dan Williams Date: Mon, 19 Mar 2018 13:10:52 -0700 Message-ID: Subject: Re: [PATCH v6 12/15] xfs: require mmap lock for xfs_break_layouts() To: Christoph Hellwig Cc: "Darrick J. Wong" , linux-nvdimm , Ross Zwisler , Dave Chinner , linux-xfs , linux-fsdevel , Jan Kara , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Mar 19, 2018 at 12:45 PM, Christoph Hellwig wrote: > On Mon, Mar 19, 2018 at 10:57:55AM -0700, Dan Williams wrote: >> I don't see anything to adapt with respect to mmap locks since reflink >> and dax are mutually exclusive. > > For now. I'll change that pretty soon. Right, so which patch set will be staged first? This one or the one that causes us to consider reflink vs dax locking?