From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v1 1/1] lib/crypto: tests: Add KUnit tests for AES
Date: Fri, 16 Jan 2026 21:20:44 +0800 [thread overview]
Message-ID: <202601162147.fF0LZSp1-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: lib/crypto/tests/aes_kunit.c:148:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260115183831.72010-2-dengler@linux.ibm.com>
References: <20260115183831.72010-2-dengler@linux.ibm.com>
TO: Holger Dengler <dengler@linux.ibm.com>
TO: Eric Biggers <ebiggers@kernel.org>
CC: Ard Biesheuvel <ardb@kernel.org>
CC: "Jason A . Donenfeld" <Jason@zx2c4.com>
CC: Herbert Xu <herbert@gondor.apana.org.au>
CC: Harald Freudenberger <freude@linux.ibm.com>
CC: Holger Dengler <dengler@linux.ibm.com>
CC: linux-kernel@vger.kernel.org
CC: linux-crypto@vger.kernel.org
Hi Holger,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 47753e09a15d9fd7cdf114550510f4f2af9333ec]
url: https://github.com/intel-lab-lkp/linux/commits/Holger-Dengler/lib-crypto-tests-Add-KUnit-tests-for-AES/20260116-030041
base: 47753e09a15d9fd7cdf114550510f4f2af9333ec
patch link: https://lore.kernel.org/r/20260115183831.72010-2-dengler%40linux.ibm.com
patch subject: [PATCH v1 1/1] lib/crypto: tests: Add KUnit tests for AES
:::::: branch date: 18 hours ago
:::::: commit date: 18 hours ago
config: s390-randconfig-r132-20260116 (https://download.01.org/0day-ci/archive/20260116/202601162147.fF0LZSp1-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260116/202601162147.fF0LZSp1-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/202601162147.fF0LZSp1-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/crypto/tests/aes_kunit.c:148:1: sparse: sparse: bad integer constant expression
lib/crypto/tests/aes_kunit.c:148:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
lib/crypto/tests/aes_kunit.c:149:1: sparse: sparse: bad integer constant expression
lib/crypto/tests/aes_kunit.c:149:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
lib/crypto/tests/aes_kunit.c:149:1: sparse: sparse: bad integer constant expression
lib/crypto/tests/aes_kunit.c:149:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +148 lib/crypto/tests/aes_kunit.c
7f9363bd920b12 Holger Dengler 2026-01-15 147
7f9363bd920b12 Holger Dengler 2026-01-15 @148 MODULE_DESCRIPTION("KUnit tests and benchmark aes library");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-16 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 13:20 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-15 18:38 [PATCH v1 0/1] lib/crypto: tests: KUnit test-suite for AES Holger Dengler
2026-01-15 18:38 ` [PATCH v1 1/1] lib/crypto: tests: Add KUnit tests " Holger Dengler
2026-01-15 20:43 ` Eric Biggers
2026-01-15 21:51 ` Holger Dengler
2026-01-15 21:58 ` Eric Biggers
2026-01-15 22:05 ` David Laight
2026-01-16 17:31 ` Holger Dengler
2026-01-16 18:37 ` David Laight
2026-01-16 19:20 ` Holger Dengler
2026-01-16 19:44 ` Eric Biggers
2026-01-16 20:55 ` Holger Dengler
2026-01-16 22:30 ` David Laight
2026-01-17 23:59 ` Eric Biggers
2026-01-16 0:25 ` kernel test robot
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=202601162147.fF0LZSp1-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.