From: Brendan Higgins via Linux-kernel-mentees <linux-kernel-mentees@lists.linuxfoundation.org>
To: Vitor Massaru Iha <vitor@massaru.org>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
KUnit Development <kunit-dev@googlegroups.com>
Subject: Re: [Linux-kernel-mentees] [PATCH] kunit: fix: kunit_binary_assert_format() only prints signed int
Date: Wed, 19 Aug 2020 14:30:03 -0700 [thread overview]
Message-ID: <CAFd5g45AuxZYY_92rOXwtVjmbaGuts+DV6WpqhHNxWYNotxq+g@mail.gmail.com> (raw)
In-Reply-To: <20200819194634.68976-1-vitor@massaru.org>
On Wed, Aug 19, 2020 at 12:46 PM Vitor Massaru Iha <vitor@massaru.org> wrote:
>
> Some tests, such as overflow_kunit(), uses unsigned int,
> But kunit_binary_assert_format() only prints signed int,
> this commit also deals with the unsigned int print.
>
> Signed-off-by: Vitor Massaru Iha <vitor@massaru.org>
> ---
> lib/kunit/assert.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/lib/kunit/assert.c b/lib/kunit/assert.c
> index 202f9fdeed0e..3ae90c09986a 100644
> --- a/lib/kunit/assert.c
> +++ b/lib/kunit/assert.c
> @@ -104,12 +104,23 @@ void kunit_binary_assert_format(const struct kunit_assert *assert,
> binary_assert->left_text,
> binary_assert->operation,
> binary_assert->right_text);
> - string_stream_add(stream, KUNIT_SUBSUBTEST_INDENT "%s == %lld\n",
> +
> + if (binary_assert->left_value - 1 < 0) {
> + string_stream_add(stream, KUNIT_SUBSUBTEST_INDENT "%s == %lld\n",
> + binary_assert->left_text,
> + binary_assert->left_value);
> + string_stream_add(stream, KUNIT_SUBSUBTEST_INDENT "%s == %lld",
> + binary_assert->right_text,
> + binary_assert->right_value);
> + }
> + else {
> + string_stream_add(stream, KUNIT_SUBSUBTEST_INDENT "%s == %llu\n",
> binary_assert->left_text,
> binary_assert->left_value);
> - string_stream_add(stream, KUNIT_SUBSUBTEST_INDENT "%s == %lld",
> + string_stream_add(stream, KUNIT_SUBSUBTEST_INDENT "%s == %llu",
> binary_assert->right_text,
> binary_assert->right_value);
> + }
I agree that you found a bug here; however, I disagree that this is
the correct fix. Given that the value is stored as a long long; isn't
the value always stored as a signed value? So if the value overflows,
won't it still not pass the check you have here?
> }
> kunit_assert_print_msg(assert, stream);
> }
>
> base-commit: d43c7fb05765152d4d4a39a8ef957c4ea14d8847
> prerequisite-patch-id: bf4b0962b0b955e4e45f5d25fece889562118158
> --
> 2.26.2
>
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-08-19 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 19:46 [Linux-kernel-mentees] [PATCH] kunit: fix: kunit_binary_assert_format() only prints signed int Vitor Massaru Iha
2020-08-19 21:30 ` Brendan Higgins via Linux-kernel-mentees [this message]
2020-08-19 21:37 ` Vitor Massaru Iha
2020-08-19 22:00 ` Vitor Massaru Iha
2020-08-19 22:19 ` Brendan Higgins via Linux-kernel-mentees
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=CAFd5g45AuxZYY_92rOXwtVjmbaGuts+DV6WpqhHNxWYNotxq+g@mail.gmail.com \
--to=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=vitor@massaru.org \
/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;
as well as URLs for NNTP newsgroup(s).