From:   "Theodore Ts'o" <tytso@mit.edu>
To:     harshadshirwadkar@gmail.com, adilger.kernel@dilger.ca,
        Xin Yin <yinxin.x@bytedance.com>
Cc:     "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org,
        linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/2] ext4: fast commit crash consistency issues
Date:   Thu, 23 Dec 2021 19:27:50 -0500
Message-Id: <164030564165.2940033.15238397285316201781.b4-ty@mit.edu>
In-Reply-To: <20211223032337.5198-1-yinxin.x@bytedance.com>
References: <20211223032337.5198-1-yinxin.x@bytedance.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 23 Dec 2021 11:23:35 +0800, Xin Yin wrote:
> This patch sets fix 2 crash-consistency issues of fast commit.
> First patch change to use ext4_ext_remove_space instead of
> ext4_punch_hole during replay delete range procedure. This
> avoid replay procedure being affeced by incorrect inode->i_size.
> Second patch correct the trank range logic for ftruncte.
> 
> After testing this patch sets with xfstests-bld, in the "log" and
> "quick" group with config "fast_commit" is selected. No regressions
> was found.
> 
> [...]

Applied, thanks!

[1/2] ext4: use ext4_ext_remove_space() for fast commit replay delete range
      commit: 20a262d66487b27133c3f8b7ac0245c2fabaa526
[2/2] ext4: fast commit may miss tracking unwritten range during ftruncate
      commit: 949197083545cbff930650f893135d30fd043d4d

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