From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 7457/9596] lib/tests/min_heap_kunit.c:208:1: sparse: sparse: bad integer constant expression
Date: Tue, 27 Jan 2026 19:47:04 +0800 [thread overview]
Message-ID: <202601271908.kGAWYFQX-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: lib/tests/min_heap_kunit.c:208:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Ryota Sakamoto <sakamo.ryota@gmail.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
Hi Ryota,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 615aad0f61e0c7a898184a394dc895c610100d4f
commit: 30edc7fafbd64d63480f6a5c8b7d919a94fde4da [7457/9596] lib/tests: convert test_min_heap module to KUnit
:::::: branch date: 12 hours ago
:::::: commit date: 6 days ago
config: loongarch-randconfig-r112-20260127 (https://download.01.org/0day-ci/archive/20260127/202601271908.kGAWYFQX-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260127/202601271908.kGAWYFQX-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202601271908.kGAWYFQX-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/tests/min_heap_kunit.c:208:1: sparse: sparse: bad integer constant expression
lib/tests/min_heap_kunit.c:208:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
lib/tests/min_heap_kunit.c:209:1: sparse: sparse: bad integer constant expression
lib/tests/min_heap_kunit.c:209:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +208 lib/tests/min_heap_kunit.c
6e24628d78e478 lib/test_min_heap.c Ian Rogers 2020-02-13 207
303474913271af lib/test_min_heap.c Jeff Johnson 2024-06-19 @208 MODULE_DESCRIPTION("Test cases for the min max heap");
:::::: The code at line 208 was first introduced by commit
:::::: 303474913271af4eb3ec1c5f955d1e01682f3e1f KUnit: add missing MODULE_DESCRIPTION() macros for lib/test_*.ko
:::::: TO: Jeff Johnson <quic_jjohnson@quicinc.com>
:::::: CC: Andrew Morton <akpm@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-27 11:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202601271908.kGAWYFQX-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.