From: "Theodore Ts'o" <tytso@mit.edu>
To: Charles Han <hanchunchao@inspur.com>
Cc: adilger.kernel@dilger.ca, shikemeng@huaweicloud.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix potential null dereference in ext4 test
Date: Fri, 21 Mar 2025 01:08:54 -0400 [thread overview]
Message-ID: <20250321050854.GC1161423@mit.edu> (raw)
In-Reply-To: <20250307115432.2112-1-hanchunchao@inspur.com>
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
Thanks, others have submitted the same fix. It's now fixed in my tree
and linux-next.
- Ted
next prev parent reply other threads:[~2025-03-21 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-08 12:32 Qasim Ijaz
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=20250321050854.GC1161423@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=hanchunchao@inspur.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shikemeng@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