Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     adilger.kernel@dilger.ca, Xin Yin <yinxin.x@bytedance.com>,
        harshadshirwadkar@gmail.com
Cc:     "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] fix blocks allocate issue during fast commit replay
Date:   Thu, 20 Jan 2022 10:44:07 -0500
Message-Id: <164269344019.116615.4300998611120334540.b4-ty@mit.edu>
In-Reply-To: <20220110035141.1980-1-yinxin.x@bytedance.com>
References: <20220110035141.1980-1-yinxin.x@bytedance.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 10 Jan 2022 11:51:39 +0800, Xin Yin wrote:
> when test fast_commit with xfstests generic/455, one failed case is
> after fast commit replay, fsck raise ’multiply-claimed blocks‘ issue.
> one inode's etb block may share with other file.
> 
> fast commit replay procedure may allocate etb blocks for inodes, but
> it may allocate blocks in use. This patch set fix this issue.
> 
> [...]

Applied, thanks!

[1/2] ext4: prevent used blocks from being allocated during fast commit replay
      commit: 8484c37da00dc121c5a9a3613b17a9c0b7b760e1
[2/2] ext4: modify the logic of ext4_mb_new_blocks_simple
      commit: 85c6392fef63e20fa2a3e82383dc57a605d6e5df

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>