From: Qasim Ijaz <qasdev00@gmail.com>
To: Charles Han <hanchunchao@inspur.com>
Cc: adilger.kernel@dilger.ca, tytso@mit.edu,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix potential null dereference in ext4 test
Date: Sat, 8 Mar 2025 12:32:42 +0000 [thread overview]
Message-ID: <Z8w43zQ2KVUPbxFi@qasdev.system> (raw)
On Fri, Mar 07, 2025 at 07:54:31PM +0800, Charles Han wrote:
> kunit_kzalloc() may return a NULL pointer, dereferencing it without
> NULL check may lead to NULL dereference.
> Add a NULL check for test_state
>
> Fixes: b7098e1fa7bc ("ext4: Add unit test for mb_free_blocks")
> Fixes: ac96b56a2fbd ("ext4: Add unit test for mb_mark_used")
> Signed-off-by: Charles Han <hanchunchao@inspur.com>
> ---
> fs/ext4/mballoc-test.c | 2 ++
> 1 file changed, 2 insertions(+)
Hi Charles,
I already submitted a patch for this on 5th March, link below:
Link: <https://lore.kernel.org/linux-ext4/20250305124012.28500-1-qasdev00@gmail.com/T/#u>
Thanks,
Qasim
>
> diff --git a/fs/ext4/mballoc-test.c b/fs/ext4/mballoc-test.c
> index bb2a223b207c..d634c12f1984 100644
> --- a/fs/ext4/mballoc-test.c
> +++ b/fs/ext4/mballoc-test.c
> @@ -796,6 +796,7 @@ static void test_mb_mark_used(struct kunit *test)
> KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buddy);
> grp = kunit_kzalloc(test, offsetof(struct ext4_group_info,
> bb_counters[MB_NUM_ORDERS(sb)]), GFP_KERNEL);
> + KUNIT_ASSERT_NOT_ERR_OR_NULL(test, grp);
>
> ret = ext4_mb_load_buddy(sb, TEST_GOAL_GROUP, &e4b);
> KUNIT_ASSERT_EQ(test, ret, 0);
> @@ -860,6 +861,7 @@ static void test_mb_free_blocks(struct kunit *test)
> KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buddy);
> grp = kunit_kzalloc(test, offsetof(struct ext4_group_info,
> bb_counters[MB_NUM_ORDERS(sb)]), GFP_KERNEL);
> + KUNIT_ASSERT_NOT_ERR_OR_NULL(test, grp);
>
> ret = ext4_mb_load_buddy(sb, TEST_GOAL_GROUP, &e4b);
> KUNIT_ASSERT_EQ(test, ret, 0);
> --
> 2.43.0
>
next reply other threads:[~2025-03-08 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 12:32 Qasim Ijaz [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-07 11:54 [PATCH] ext4: Fix potential null dereference in ext4 test Charles Han
2025-03-10 9:35 ` Kemeng Shi
2025-03-21 5:08 ` Theodore Ts'o
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=Z8w43zQ2KVUPbxFi@qasdev.system \
--to=qasdev00@gmail.com \
--cc=20250307115432.2112-1-hanchunchao@inspur.com \
--cc=adilger.kernel@dilger.ca \
--cc=hanchunchao@inspur.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.