From: kernel test robot <lkp@intel.com>
To: Holger Dengler <dengler@linux.ibm.com>,
Eric Biggers <ebiggers@kernel.org>,
David Laight <david.laight.linux@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Harald Freudenberger <freude@linux.ibm.com>,
Holger Dengler <dengler@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v2 1/1] lib/crypto: tests: Add KUnit tests for AES
Date: Tue, 20 Jan 2026 04:31:28 +0800 [thread overview]
Message-ID: <202601200403.mo4FMAVa-lkp@intel.com> (raw)
In-Reply-To: <20260119121210.2662-2-dengler@linux.ibm.com>
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/20260119-201615
base: 47753e09a15d9fd7cdf114550510f4f2af9333ec
patch link: https://lore.kernel.org/r/20260119121210.2662-2-dengler%40linux.ibm.com
patch subject: [PATCH v2 1/1] lib/crypto: tests: Add KUnit tests for AES
config: xtensa-randconfig-r133-20260120 (https://download.01.org/0day-ci/archive/20260120/202601200403.mo4FMAVa-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260120/202601200403.mo4FMAVa-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/oe-kbuild-all/202601200403.mo4FMAVa-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
lib/crypto/tests/aes_kunit.c: note: in included file (through arch/xtensa/include/asm/atomic.h, include/linux/atomic.h, include/linux/jump_label.h, ...):
arch/xtensa/include/asm/processor.h:105:2: sparse: sparse: Unsupported xtensa ABI
arch/xtensa/include/asm/processor.h:135:2: sparse: sparse: Unsupported Xtensa ABI
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(description, ...) contains embedded NUL byte"
lib/crypto/tests/aes_kunit.c:150:1: sparse: sparse: bad integer constant expression
lib/crypto/tests/aes_kunit.c:150:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
lib/crypto/tests/aes_kunit.c:150:1: sparse: sparse: bad integer constant expression
lib/crypto/tests/aes_kunit.c:150:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
>> lib/crypto/tests/aes_kunit.c:35:26: sparse: sparse: incompatible types in conditional expression (incompatible argument 1 (different base types)):
lib/crypto/tests/aes_kunit.c:35:26: sparse: void ( * )( ... )
lib/crypto/tests/aes_kunit.c:35:26: sparse: void ( * )( ... )
>> lib/crypto/tests/aes_kunit.c:35:26: sparse: sparse: incompatible types in conditional expression (incompatible argument 1 (different base types)):
lib/crypto/tests/aes_kunit.c:35:26: sparse: void ( * )( ... )
lib/crypto/tests/aes_kunit.c:35:26: sparse: void ( * )( ... )
vim +35 lib/crypto/tests/aes_kunit.c
28
29 static __always_inline u64 time_aes_op(bool encrypt, struct aes_key *aes_key,
30 u8 *out, const u8 *in)
31 {
32 void (*aes_op)(const struct aes_key *key, u8 *out, const u8 *in);
33 u64 t;
34
> 35 aes_op = encrypt ? &aes_encrypt : &aes_decrypt;
36
37 preempt_disable();
38 t = ktime_get_ns();
39 aes_op(aes_key, out, in);
40 t = ktime_get_ns() - t;
41 preempt_enable();
42
43 return t;
44 }
45
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-19 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 12:12 [PATCH v2 0/1] lib/crypto: tests: KUnit test-suite for AES Holger Dengler
2026-01-19 12:12 ` [PATCH v2 1/1] lib/crypto: tests: Add KUnit tests " Holger Dengler
2026-01-19 16:39 ` kernel test robot
2026-01-19 17:22 ` kernel test robot
2026-01-19 20:31 ` kernel test robot [this message]
2026-01-29 1:18 ` Eric Biggers
2026-01-30 10:54 ` Holger Dengler
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=202601200403.mo4FMAVa-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=dengler@linux.ibm.com \
--cc=ebiggers@kernel.org \
--cc=freude@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox