Received-SPF: pass (google.com: domain of linux-kernel+bounces-162178-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
References: <20240320110548.2200662-1-yi.zhang@huaweicloud.com>
 <20240425-modeerscheinung-ortstarif-bf25f0e3e6f3@brauner>
User-agent: mu4e 1.10.8; emacs 29.2
From: Chandan Babu R <chandanbabu@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Zhang Yi <yi.zhang@huaweicloud.com>, linux-kernel@vger.kernel.org,
 djwong@kernel.org, hch@infradead.org, david@fromorbit.com, tytso@mit.edu,
 jack@suse.cz, yi.zhang@huawei.com, chengzhihao1@huawei.com,
 yukuai3@huawei.com, linux-xfs@vger.kernel.org,
 linux-fsdevel@vger.kernel.org
Subject: Re: (subset) [PATCH v4 0/9] xfs/iomap: fix non-atomic clone
 operation and don't update size when zeroing range post eof
Date: Mon, 29 Apr 2024 17:18:52 +0530
In-reply-to: <20240425-modeerscheinung-ortstarif-bf25f0e3e6f3@brauner>
Message-ID: <87o79spevy.fsf@debian-BULLSEYE-live-builder-AMD64>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

On Thu, Apr 25, 2024 at 02:25:47 PM +0200, Christian Brauner wrote:
> On Wed, 20 Mar 2024 19:05:39 +0800, Zhang Yi wrote:
>> Changes since v3:
>>  - Improve some git message comments and do some minor code cleanup, no
>>    logic changes.
>> 
>> Changes since v2:
>>  - Merge the patch for dropping of xfs_convert_blocks() and the patch
>>    for modifying xfs_bmapi_convert_delalloc().
>>  - Reword the commit message of the second patch.
>> 
>> [...]
>
> @Chandan, since the bug has been determined to be in the xfs specific changes
> for this I've picked up the cleanup patches into vfs.iomap. If you need to rely
> on that branch I can keep it stable.

I am sorry about the late reply. I somehow missed this mail.

I will pick up the XFS specific patches now.

-- 
Chandan