From:   "Theodore Ts'o" <tytso@mit.edu>
To:     jack@suse.com, zhanchengbin <zhanchengbin1@huawei.com>
Cc:     "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org,
        liuzhiqiang26@huawei.com, yebin10@huawei.com, yi.zhang@huawei.com,
        linfeilong@huawei.com
Subject: Re: [PATCH] ext4: fix inode tree inconsistency caused by ENOMEM
Date:   Sun, 19 Feb 2023 00:40:54 -0500
Message-Id: <167678522163.2723470.4254795729575378394.b4-ty@mit.edu>
In-Reply-To: <20230103022812.130603-1-zhanchengbin1@huawei.com>
References: <20230103022812.130603-1-zhanchengbin1@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 3 Jan 2023 10:28:12 +0800, zhanchengbin wrote:
> If ENOMEM fails when the extent is splitting, we need to restore the length
> of the split extent.
> In the ext4_split_extent_at function, only in ext4_ext_create_new_leaf will
> it alloc memory and change the shape of the extent tree,even if an ENOMEM
> is returned at this time, the extent tree is still self-consistent, Just
> restore the split extent lens in the function ext4_split_extent_at.
> 
> [...]

Applied, thanks!

[1/1] ext4: fix inode tree inconsistency caused by ENOMEM
      commit: 3f5424790d4377839093b68c12b130077a4e4510

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