From: Kees Cook <kees@kernel.org>
To: Erhard Furtner <erhard_f@mailbox.org>
Cc: linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com,
Alessandro Carminati <acarmina@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: WARNING: CPU: 27 PID: 7051 at lib/math/int_log.c:63 intlog2+0xaa/0xe0 at running int_log_kunit test (v6.15-rc1)
Date: Wed, 7 Jan 2026 12:35:10 -0800 [thread overview]
Message-ID: <202601071229.C721443D5@keescook> (raw)
In-Reply-To: <eaa389d3-00e2-4418-be8a-bed009429a73@mailbox.org>
On Tue, Jan 06, 2026 at 11:17:33PM +0100, Erhard Furtner wrote:
> Greetings!
>
> Still getting this warning on kernel v6.18.3 and v6.19-rc4 when running
> int_log_kunit test via modprobe on my systems (x86_64, x86, ppc). This dmesg
> is from my Intel Core Ultra 7 265F system:
>
> [...]
> KTAP version 1
> 1..1
> KTAP version 1
> # Subtest: math-int_log
> # module: int_log_kunit
> 1..2
> KTAP version 1
> # Subtest: intlog2_test
> ------------[ cut here ]------------
> 1
> WARNING: lib/math/int_log.c:63 at intlog2+0x59/0x70, CPU#16:
This is:
if (unlikely(value == 0)) {
WARN_ON(1);
return 0;
}
> [...]
> ? kthreads_online_cpu+0xf0/0xf0
> ? kthreads_online_cpu+0xf0/0xf0
> ret_from_fork_asm+0x11/0x20
> </TASK>
> ---[ end trace 0000000000000000 ]---
> ok 1 Log base 2 of 0
Whcih seems to be exactly what is being tested...
It seems like we have another case of needed to silence warnings under
kunit[1]. Alessandro and Peter, where does the linked series stand
currently?
-Kees
[1] https://lore.kernel.org/lkml/20250526132755.166150-1-acarmina@redhat.com/
--
Kees Cook
next prev parent reply other threads:[~2026-01-07 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 18:02 WARNING: CPU: 27 PID: 7051 at lib/math/int_log.c:63 intlog2+0xaa/0xe0 at running int_log_kunit test (v6.15-rc1) Erhard Furtner
2025-04-21 10:22 ` Erhard Furtner
2026-01-06 22:17 ` Erhard Furtner
2026-01-07 20:35 ` Kees Cook [this message]
2026-01-07 21:46 ` Peter Zijlstra
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=202601071229.C721443D5@keescook \
--to=kees@kernel.org \
--cc=acarmina@redhat.com \
--cc=erhard_f@mailbox.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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