From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [akpm-mm:mm-nonmm-unstable 97/158] lib/tests/liveupdate.c:156:1: sparse: sparse: bad integer constant expression
Date: Sun, 18 Jan 2026 05:19:22 +0800 [thread overview]
Message-ID: <202601180507.eJetLj26-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: lib/tests/liveupdate.c:156:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: David Hildenbrand <david@kernel.org>
TO: Pasha Tatashin <pasha.tatashin@soleen.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
head: dcaca77bf6d52becda62f4837a3b03bcce1a0766
commit: 30bcf37b0bb7d238b549d33ee3621724d0d2653b [97/158] tests/liveupdate: add in-kernel liveupdate test
:::::: branch date: 17 hours ago
:::::: commit date: 17 hours ago
config: x86_64-randconfig-r133-20260118 (https://download.01.org/0day-ci/archive/20260118/202601180507.eJetLj26-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260118/202601180507.eJetLj26-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/202601180507.eJetLj26-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/tests/liveupdate.c:156:1: sparse: sparse: bad integer constant expression
lib/tests/liveupdate.c:156:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
>> lib/tests/liveupdate.c:156:1: sparse: sparse: bad integer constant expression
lib/tests/liveupdate.c:156:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
lib/tests/liveupdate.c:157:1: sparse: sparse: bad integer constant expression
lib/tests/liveupdate.c:157:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
lib/tests/liveupdate.c:158:1: sparse: sparse: bad integer constant expression
lib/tests/liveupdate.c:158:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
vim +156 lib/tests/liveupdate.c
30bcf37b0bb7d2 Pasha Tatashin 2025-12-18 155
30bcf37b0bb7d2 Pasha Tatashin 2025-12-18 @156 MODULE_LICENSE("GPL");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-17 21:20 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=202601180507.eJetLj26-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.