[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4hhM3py_YG-qYcAxsqdCZT1aM+ziKffijVManPngbCg_A@mail.gmail.com>
Date: Mon, 19 Mar 2018 13:10:52 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Christoph Hellwig <hch@....de>
Cc: "Darrick J. Wong" <darrick.wong@...cle.com>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Dave Chinner <david@...morbit.com>,
linux-xfs <linux-xfs@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Jan Kara <jack@...e.cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 12/15] xfs: require mmap lock for xfs_break_layouts()
On Mon, Mar 19, 2018 at 12:45 PM, Christoph Hellwig <hch@....de> 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?
Powered by blists - more mailing lists