All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [ebiggers:wip-aes 2/53] lib/crypto/tests/mldsa_kunit.c:436:1: sparse: sparse: bad integer constant expression
Date: Sat, 10 Jan 2026 20:03:19 +0800	[thread overview]
Message-ID: <202601101941.XTccLEle-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: lib/crypto/tests/mldsa_kunit.c:436:1: sparse: sparse: bad integer constant expression"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Eric Biggers <ebiggers@kernel.org>
CC: David Howells <dhowells@redhat.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git wip-aes
head:   237c28fcac1381425254d1af768fb806678910bd
commit: ff08ac38bcf2445e5b247c482e94ab3aca573382 [2/53] lib/crypto: tests: Add KUnit tests for ML-DSA verification
:::::: branch date: 9 hours ago
:::::: commit date: 5 days ago
config: sh-randconfig-r113-20260110 (https://download.01.org/0day-ci/archive/20260110/202601101941.XTccLEle-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260110/202601101941.XTccLEle-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/202601101941.XTccLEle-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> lib/crypto/mldsa.c:651:1: sparse: sparse: bad integer constant expression
   lib/crypto/mldsa.c:651:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
   lib/crypto/mldsa.c:652:1: sparse: sparse: bad integer constant expression
   lib/crypto/mldsa.c:652:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
--
>> lib/crypto/tests/mldsa_kunit.c:436:1: sparse: sparse: bad integer constant expression
   lib/crypto/tests/mldsa_kunit.c:436:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
   lib/crypto/tests/mldsa_kunit.c:437:1: sparse: sparse: bad integer constant expression
   lib/crypto/tests/mldsa_kunit.c:437:1: sparse: sparse: static assertion failed: "MODULE_INFO(import_ns, ...) contains embedded NUL byte"
   lib/crypto/tests/mldsa_kunit.c:438:1: sparse: sparse: bad integer constant expression
   lib/crypto/tests/mldsa_kunit.c:438:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"

vim +436 lib/crypto/tests/mldsa_kunit.c

ff08ac38bcf244 Eric Biggers 2025-12-14  435  
ff08ac38bcf244 Eric Biggers 2025-12-14 @436  MODULE_DESCRIPTION("KUnit tests and benchmark for ML-DSA");

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-01-10 12:03 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=202601101941.XTccLEle-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.