Received-SPF: pass (google.com: domain of linux-ext4+bounces-2351-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, libaokun@huaweicloud.com
Cc: "Theodore Ts'o" <tytso@mit.edu>, adilger.kernel@dilger.ca, jack@suse.cz,
        ritesh.list@gmail.com, linux-kernel@vger.kernel.org,
        yi.zhang@huawei.com, yangerkun@huawei.com,
        Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH 0/2] ext4: fix WARNING in mb_cache_destroy
Date: Tue,  7 May 2024 19:03:51 -0400
Message-ID: <171512302202.3602678.10418698281997771278.b4-ty@mit.edu>
In-Reply-To: <20240504075526.2254349-1-libaokun@huaweicloud.com>
References: <20240504075526.2254349-1-libaokun@huaweicloud.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit


On Sat, 04 May 2024 15:55:24 +0800, libaokun@huaweicloud.com wrote:
> Baokun Li (2):
>   ext4: fix mb_cache_entry's e_refcnt leak in
>     ext4_xattr_block_cache_find()
>   ext4: propagate errors from ext4_sb_bread() in
>     ext4_xattr_block_cache_find()
> 
> fs/ext4/xattr.c | 23 ++++++++++++++---------
>  1 file changed, 14 insertions(+), 9 deletions(-)
> 
> [...]

Applied, thanks!

[1/2] ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find()
      commit: 0c0b4a49d3e7f49690a6827a41faeffad5df7e21
[2/2] ext4: propagate errors from ext4_sb_bread() in ext4_xattr_block_cache_find()
      commit: dc1c4663bc493f323d6b2f9dd55c044ea920dacf

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