From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail105.syd.optusnet.com.au (mail105.syd.optusnet.com.au [211.29.132.249]) by smtp.subspace.kernel.org (Postfix) with ESMTP id BA52046A8 for ; Thu, 21 Apr 2022 07:46:59 +0000 (UTC) Received: from dread.disaster.area (pa49-181-115-138.pa.nsw.optusnet.com.au [49.181.115.138]) by mail105.syd.optusnet.com.au (Postfix) with ESMTPS id 2C10310E5C0F; Thu, 21 Apr 2022 17:46:55 +1000 (AEST) Received: from dave by dread.disaster.area with local (Exim 4.92.3) (envelope-from ) id 1nhRWf-002hck-5w; Thu, 21 Apr 2022 17:46:53 +1000 Date: Thu, 21 Apr 2022 17:46:53 +1000 From: Dave Chinner To: Christoph Hellwig Cc: Dan Williams , Shiyang Ruan , Linux Kernel Mailing List , linux-xfs , Linux NVDIMM , Linux MM , linux-fsdevel , "Darrick J. Wong" , Jane Chu , Andrew Morton , Naoya Horiguchi Subject: Re: [PATCH v13 0/7] fsdax: introduce fs query to support reflink Message-ID: <20220421074653.GT1544202@dread.disaster.area> References: <20220419045045.1664996-1-ruansy.fnst@fujitsu.com> <20220421012045.GR1544202@dread.disaster.area> <86cb0ada-208c-02de-dbc9-53c6014892c3@fujitsu.com> <20220421043502.GS1544202@dread.disaster.area> Precedence: bulk X-Mailing-List: nvdimm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.4 cv=e9dl9Yl/ c=1 sm=1 tr=0 ts=62610bf2 a=/kVtbFzwtM2bJgxRVb+eeA==:117 a=/kVtbFzwtM2bJgxRVb+eeA==:17 a=kj9zAlcOel0A:10 a=z0gMJWrwH1QA:10 a=7-415B0cAAAA:8 a=Mb5XfCdAhjU6mY5isQ0A:9 a=CjuIK1q_8ugA:10 a=biEYGPWJfzWAr4FL6Ov7:22 On Wed, Apr 20, 2022 at 10:54:59PM -0700, Christoph Hellwig wrote: > On Thu, Apr 21, 2022 at 02:35:02PM +1000, Dave Chinner wrote: > > Sure, I'm not a maintainer and just the stand-in patch shepherd for > > a single release. However, being unable to cleanly merge code we > > need integrated into our local subsystem tree for integration > > testing because a patch dependency with another subsystem won't gain > > a stable commit ID until the next merge window is .... distinctly > > suboptimal. > > Yes. Which is why we've taken a lot of mm patchs through other trees, > sometimes specilly crafted for that. So I guess in this case we'll > just need to take non-trivial dependencies into the XFS tree, and just > deal with small merge conflicts for the trivial ones. OK. As Naoyo has pointed out, the first dependency/conflict Ruan has listed looks trivial to resolve. The second dependency, OTOH, is on a new function added in the patch pointed to. That said, at first glance it looks to be independent of the first two patches in that series so I might just be able to pull that one patch in and have that leave us with a working fsdax+reflink tree. Regardless, I'll wait to see how much work the updated XFS/DAX reflink enablement patchset still requires when Ruan posts it before deciding what to do here. If it isn't going to be a merge candidate, what to do with this patchset is moot because there's little to test without reflink enabled... Cheers, Dave. -- Dave Chinner david@fromorbit.com