Received-SPF: pass (google.com: domain of linux-ext4-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:     Zhang Yi <yi.zhang@huawei.com>, linux-ext4@vger.kernel.org
Cc:     "Theodore Ts'o" <tytso@mit.edu>, yukuai3@huawei.com, jack@suse.cz,
        adilger.kernel@dilger.ca
Subject: Re: [RFC PATCH 0/3] ext4: enhance extent consistency check
Date:   Wed, 13 Oct 2021 22:32:39 -0400
Message-Id: <163416151699.223555.16012336427055541414.b4-ty@mit.edu>
In-Reply-To: <20210908120850.4012324-1-yi.zhang@huawei.com>
References: <20210908120850.4012324-1-yi.zhang@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 8 Sep 2021 20:08:47 +0800, Zhang Yi wrote:
> Now that in the error patch of extent updating procedure cannot handle
> error and roll-back partial updates properly, so we could access the
> left inconsistent extent buffer later and lead to BUGON in
> errors=continue mode. For example, we could get below BUGON if we
> update leaf extent but failed to update index extent in
> ext4_ext_insert_extent() and try to alloc block again.
> 
> [...]

Applied, thanks!

[1/3] ext4: check for out-of-order index extents in ext4_valid_extent_entries()
      commit: efbcc1015b07e3e8bafa97394b743812c180a9dd
[2/3] ext4: check for inconsistent extents between index and leaf block
      commit: a992bc717652fb15b435884c587ae5249415239c
[3/3] ext4: prevent partial update of the extent blocks
      commit: 916ff8d5ea0e24fd43f113b6b5326d5ea8f68310

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