From: Pei Xiao <xiaopei01@kylinos.cn>
To: Jonathan Cameron <jic23@kernel.org>
Cc: liambeguin@gmail.com, lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, xiaopeitux@foxmail.com
Subject: Re: [PATCH] iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale
Date: Mon, 4 Nov 2024 09:14:45 +0800 [thread overview]
Message-ID: <34ab4d22-0b07-43ba-9d4f-eb4b2867f36a@kylinos.cn> (raw)
In-Reply-To: <20241101172926.4e8e3f43@jic23-huawei>
On 2024/11/2 01:29, Jonathan Cameron Wrote:
> On Wed, 30 Oct 2024 11:48:54 +0800
> Pei Xiao <xiaopei01@kylinos.cn> wrote:
>
>> kunit_kmalloc may fail, return value might be NULL and will cause
>> NULL pointer dereference.Add KUNIT_ASSERT_NOT_ERR_OR_NULL fix it.
> Can it be an error? If not why not use KUNIT_ASSERT_NOT_NULL?
As you thought, initially I felt that we should use
KUNIT_ASSERT_NOT_NULL. However, when I used grep
KUNIT_ASSERT_NOT_ERR_OR_NULL -nr drivers/iio/test/, I found that the
drivers/iio/test/ directory exclusively uses
KUNIT_ASSERT_NOT_ERR_OR_NULL instead of KUNIT_ASSERT_NOT_NULL. To
maintain consistency, I have changed it to KUNIT_ASSERT_NOT_ERR_OR_NULL.
drivers/iio/test/iio-test-format.c:22:
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
drivers/iio/test/iio-test-format.c:52:
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
drivers/iio/test/iio-test-format.c:113:
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
drivers/iio/test/iio-test-format.c:153:
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
drivers/iio/test/iio-test-format.c:193:
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
drivers/iio/test/iio-test-format.c:208:
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
>>
>> Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
>> Fixes: 8e74a48d17d5 ("iio: test: add basic tests for the iio-rescale driver")
>> ---
>> drivers/iio/test/iio-test-rescale.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/iio/test/iio-test-rescale.c b/drivers/iio/test/iio-test-rescale.c
>> index 31ee55a6faed..11bfff6636a3 100644
>> --- a/drivers/iio/test/iio-test-rescale.c
>> +++ b/drivers/iio/test/iio-test-rescale.c
>> @@ -652,6 +652,8 @@ static void iio_rescale_test_scale(struct kunit *test)
>> int rel_ppm;
>> int ret;
>>
>> + KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buff);
>> +
>> rescale.numerator = t->numerator;
>> rescale.denominator = t->denominator;
>> rescale.offset = t->offset;
>> @@ -681,6 +683,8 @@ static void iio_rescale_test_offset(struct kunit *test)
>> int values[2];
>> int ret;
>>
>> + KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buff_off);
>> +
>> rescale.numerator = t->numerator;
>> rescale.denominator = t->denominator;
>> rescale.offset = t->offset;
>
next prev parent reply other threads:[~2024-11-04 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 3:48 Pei Xiao
2024-11-01 17:29 ` Jonathan Cameron
2024-11-04 1:14 ` Pei Xiao [this message]
2024-11-23 14:29 ` Jonathan Cameron
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=34ab4d22-0b07-43ba-9d4f-eb4b2867f36a@kylinos.cn \
--to=xiaopei01@kylinos.cn \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaopeitux@foxmail.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
all inboxes | Powered by JetHome®