[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87o79spevy.fsf@debian-BULLSEYE-live-builder-AMD64>
Date: Mon, 29 Apr 2024 17:18:52 +0530
From: Chandan Babu R <chandanbabu@...nel.org>
To: Christian Brauner <brauner@...nel.org>
Cc: Zhang Yi <yi.zhang@...weicloud.com>, linux-kernel@...r.kernel.org,
djwong@...nel.org, hch@...radead.org, david@...morbit.com, tytso@....edu,
jack@...e.cz, yi.zhang@...wei.com, chengzhihao1@...wei.com,
yukuai3@...wei.com, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.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
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
Powered by blists - more mailing lists