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 v3 2/5] ext4: fix miss unlock 'sb->s_umount' in extents_kunit_init()
Date: Sat, 14 Mar 2026 17:51:45 +0530 [thread overview]
Message-ID: <ikaytxd2.ritesh.list@gmail.com> (raw)
In-Reply-To: <20260314074903.1314851-3-yebin@huaweicloud.com>
Ye Bin <yebin@huaweicloud.com> writes:
> From: Ye Bin <yebin10@huawei.com>
>
> There's warning as follows when do ext4 kunit test:
> WARNING: kunit_try_catch/15923 still has locks held!
> 7.0.0-rc3-next-20260309-00028-g73f965a1bbb1-dirty #281 Tainted: G E N
> 1 lock held by kunit_try_catch/15923:
> #0: ffff888139f860e0 (&type->s_umount_key#70/1){+.+.}-{4:4}, at: alloc_super.constprop.0+0x172/0xa90
> Call Trace:
> <TASK>
> dump_stack_lvl+0x180/0x1b0
> debug_check_no_locks_held+0xc8/0xd0
> do_exit+0x1502/0x2b20
> kthread+0x3a9/0x540
> ret_from_fork+0xa76/0xdf0
> ret_from_fork_asm+0x1a/0x30
>
> As sget() will return 'sb' which holds 's->s_umount' lock. However,
> "extents-test" miss unlock this lock.
> So unlock 's->s_umount' in the end of extents_kunit_init().
>
Agreed.
LGTM.
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
> Fixes: cb1e0c1d1fad ("ext4: kunit tests for extent splitting and conversion")
> Signed-off-by: Ye Bin <yebin10@huawei.com>
> ---
> fs/ext4/extents-test.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ext4/extents-test.c b/fs/ext4/extents-test.c
> index e3d23e3cda87..3d4663d99eb1 100644
> --- a/fs/ext4/extents-test.c
> +++ b/fs/ext4/extents-test.c
> @@ -310,6 +310,8 @@ static int extents_kunit_init(struct kunit *test)
> kunit_activate_static_stub(test, ext4_ext_zeroout, ext4_ext_zeroout_stub);
> kunit_activate_static_stub(test, ext4_issue_zeroout,
> ext4_issue_zeroout_stub);
> + up_write(&sb->s_umount);
> +
> return 0;
> }
>
> --
> 2.34.1
next prev parent reply other threads:[~2026-03-14 12:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 7:48 [PATCH v3 0/5] Fix some issues about ext4-test Ye Bin
2026-03-14 7:48 ` [PATCH v3 1/5] ext4: call deactivate_super() in extents_kunit_exit() Ye Bin
2026-03-14 12:19 ` Ritesh Harjani
2026-03-15 5:39 ` Ojaswin Mujoo
2026-03-18 2:21 ` yebin (H)
2026-03-14 7:49 ` [PATCH v3 2/5] ext4: fix miss unlock 'sb->s_umount' in extents_kunit_init() Ye Bin
2026-03-14 12:21 ` Ritesh Harjani [this message]
2026-03-15 5:40 ` Ojaswin Mujoo
2026-03-14 7:49 ` [PATCH v3 3/5] ext4: fix the error handling process in extents_kunit_init) Ye Bin
2026-03-14 12:29 ` Ritesh Harjani
2026-03-16 1:36 ` yebin (H)
2026-03-15 6:12 ` Ojaswin Mujoo
2026-03-14 7:49 ` [PATCH v3 4/5] ext4: fix possible null-ptr-deref in extents_kunit_exit() Ye Bin
2026-03-14 12:35 ` Ritesh Harjani
2026-03-15 6:13 ` Ojaswin Mujoo
2026-03-14 7:49 ` [PATCH v3 5/5] ext4: fix possible null-ptr-deref in mbt_kunit_exit() Ye Bin
2026-03-14 12:36 ` Ritesh Harjani
2026-03-15 6:23 ` Ojaswin Mujoo
2026-03-14 12:04 ` [PATCH v3 0/5] Fix some issues about ext4-test Ritesh Harjani
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=ikaytxd2.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