From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Ye Bin <yebin@huaweicloud.com>,
tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org
Cc: jack@suse.cz
Subject: Re: [PATCH v5 3/5] ext4: fix the error handling process in extents_kunit_init).
Date: Thu, 02 Apr 2026 05:51:58 +0530 [thread overview]
Message-ID: <ldf6mct5.ritesh.list@gmail.com> (raw)
In-Reply-To: <20260330133035.287842-4-yebin@huaweicloud.com>
Ye Bin <yebin@huaweicloud.com> writes:
> From: Ye Bin <yebin10@huawei.com>
>
> The error processing in extents_kunit_init() is improper, causing
> resource leakage.
> Reconstruct the error handling process to prevent potential resource
> leaks
>
> Fixes: cb1e0c1d1fad ("ext4: kunit tests for extent splitting and conversion")
> Signed-off-by: Ye Bin <yebin10@huawei.com>
> ---
> fs/ext4/extents-test.c | 50 +++++++++++++++++++++++++++++-------------
> 1 file changed, 35 insertions(+), 15 deletions(-)
Looks better now. Thanks for taking care of it.
Feel free to add:
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
next prev parent reply other threads:[~2026-04-02 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 13:30 [PATCH v5 0/5] Fix some issues about ext4-test Ye Bin
2026-03-30 13:30 ` [PATCH v5 1/5] ext4: fix miss unlock 'sb->s_umount' in extents_kunit_init() Ye Bin
2026-03-30 13:30 ` [PATCH v5 2/5] ext4: call deactivate_super() in extents_kunit_exit() Ye Bin
2026-03-30 13:30 ` [PATCH v5 3/5] ext4: fix the error handling process in extents_kunit_init) Ye Bin
2026-04-01 7:34 ` Ojaswin Mujoo
2026-04-02 0:21 ` Ritesh Harjani [this message]
2026-03-30 13:30 ` [PATCH v5 4/5] ext4: fix possible null-ptr-deref in extents_kunit_exit() Ye Bin
2026-03-30 13:30 ` [PATCH v5 5/5] ext4: fix possible null-ptr-deref in mbt_kunit_exit() Ye Bin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ldf6mct5.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yebin@huaweicloud.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox