From: kernel test robot <lkp@intel.com>
To: "Rusydi H. Makarim" <rusydi.makarim@kriptograf.id>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Eric Biggers <ebiggers@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Ard Biesheuvel <ardb@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
"Rusydi H. Makarim" <rusydi.makarim@kriptograf.id>
Subject: Re: [PATCH 2/3] lib/crypto: Initial implementation of Ascon-Hash256
Date: Tue, 16 Dec 2025 07:01:26 +0800 [thread overview]
Message-ID: <202512160656.DWMVkABi-lkp@intel.com> (raw)
In-Reply-To: <20251215-ascon_hash256-v1-2-24ae735e571e@kriptograf.id>
Hi Rusydi,
kernel test robot noticed the following build errors:
[auto build test ERROR on ebiggers/libcrypto-next]
[also build test ERROR on ebiggers/libcrypto-fixes linus/master v6.19-rc1 next-20251215]
[cannot apply to herbert-cryptodev-2.6/master herbert-crypto-2.6/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Rusydi-H-Makarim/lib-crypto-Initial-implementation-of-Ascon-Hash256/20251215-165442
base: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git libcrypto-next
patch link: https://lore.kernel.org/r/20251215-ascon_hash256-v1-2-24ae735e571e%40kriptograf.id
patch subject: [PATCH 2/3] lib/crypto: Initial implementation of Ascon-Hash256
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20251216/202512160656.DWMVkABi-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/20251216/202512160656.DWMVkABi-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/202512160656.DWMVkABi-lkp@intel.com/
All errors (new ones prefixed by >>):
>> lib/crypto/hash_info.c:35:3: error: use of undeclared identifier 'HASH_ALGO_ASCON_HASH256'
35 | [HASH_ALGO_ASCON_HASH256] = "ascon-hash256",
| ^
>> lib/crypto/hash_info.c:63:30: error: use of undeclared identifier 'ASCON_HASH256_DIGEST_SIZE'
63 | [HASH_ALGO_ASCON_HASH256] = ASCON_HASH256_DIGEST_SIZE,
| ^
lib/crypto/hash_info.c:63:3: error: use of undeclared identifier 'HASH_ALGO_ASCON_HASH256'
63 | [HASH_ALGO_ASCON_HASH256] = ASCON_HASH256_DIGEST_SIZE,
| ^
3 errors generated.
vim +/HASH_ALGO_ASCON_HASH256 +35 lib/crypto/hash_info.c
10
11 const char *const hash_algo_name[HASH_ALGO__LAST] = {
12 [HASH_ALGO_MD4] = "md4",
13 [HASH_ALGO_MD5] = "md5",
14 [HASH_ALGO_SHA1] = "sha1",
15 [HASH_ALGO_RIPE_MD_160] = "rmd160",
16 [HASH_ALGO_SHA256] = "sha256",
17 [HASH_ALGO_SHA384] = "sha384",
18 [HASH_ALGO_SHA512] = "sha512",
19 [HASH_ALGO_SHA224] = "sha224",
20 [HASH_ALGO_RIPE_MD_128] = "rmd128",
21 [HASH_ALGO_RIPE_MD_256] = "rmd256",
22 [HASH_ALGO_RIPE_MD_320] = "rmd320",
23 [HASH_ALGO_WP_256] = "wp256",
24 [HASH_ALGO_WP_384] = "wp384",
25 [HASH_ALGO_WP_512] = "wp512",
26 [HASH_ALGO_TGR_128] = "tgr128",
27 [HASH_ALGO_TGR_160] = "tgr160",
28 [HASH_ALGO_TGR_192] = "tgr192",
29 [HASH_ALGO_SM3_256] = "sm3",
30 [HASH_ALGO_STREEBOG_256] = "streebog256",
31 [HASH_ALGO_STREEBOG_512] = "streebog512",
32 [HASH_ALGO_SHA3_256] = "sha3-256",
33 [HASH_ALGO_SHA3_384] = "sha3-384",
34 [HASH_ALGO_SHA3_512] = "sha3-512",
> 35 [HASH_ALGO_ASCON_HASH256] = "ascon-hash256",
36 };
37 EXPORT_SYMBOL_GPL(hash_algo_name);
38
39 const int hash_digest_size[HASH_ALGO__LAST] = {
40 [HASH_ALGO_MD4] = MD5_DIGEST_SIZE,
41 [HASH_ALGO_MD5] = MD5_DIGEST_SIZE,
42 [HASH_ALGO_SHA1] = SHA1_DIGEST_SIZE,
43 [HASH_ALGO_RIPE_MD_160] = RMD160_DIGEST_SIZE,
44 [HASH_ALGO_SHA256] = SHA256_DIGEST_SIZE,
45 [HASH_ALGO_SHA384] = SHA384_DIGEST_SIZE,
46 [HASH_ALGO_SHA512] = SHA512_DIGEST_SIZE,
47 [HASH_ALGO_SHA224] = SHA224_DIGEST_SIZE,
48 [HASH_ALGO_RIPE_MD_128] = RMD128_DIGEST_SIZE,
49 [HASH_ALGO_RIPE_MD_256] = RMD256_DIGEST_SIZE,
50 [HASH_ALGO_RIPE_MD_320] = RMD320_DIGEST_SIZE,
51 [HASH_ALGO_WP_256] = WP256_DIGEST_SIZE,
52 [HASH_ALGO_WP_384] = WP384_DIGEST_SIZE,
53 [HASH_ALGO_WP_512] = WP512_DIGEST_SIZE,
54 [HASH_ALGO_TGR_128] = TGR128_DIGEST_SIZE,
55 [HASH_ALGO_TGR_160] = TGR160_DIGEST_SIZE,
56 [HASH_ALGO_TGR_192] = TGR192_DIGEST_SIZE,
57 [HASH_ALGO_SM3_256] = SM3256_DIGEST_SIZE,
58 [HASH_ALGO_STREEBOG_256] = STREEBOG256_DIGEST_SIZE,
59 [HASH_ALGO_STREEBOG_512] = STREEBOG512_DIGEST_SIZE,
60 [HASH_ALGO_SHA3_256] = SHA3_256_DIGEST_SIZE,
61 [HASH_ALGO_SHA3_384] = SHA3_384_DIGEST_SIZE,
62 [HASH_ALGO_SHA3_512] = SHA3_512_DIGEST_SIZE,
> 63 [HASH_ALGO_ASCON_HASH256] = ASCON_HASH256_DIGEST_SIZE,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2025-12-15 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251215-ascon_hash256-v1-2-24ae735e571e@kriptograf.id>
2025-12-15 23:01 ` kernel test robot [this message]
2025-12-20 15:34 ` [PATCH 2/3] lib/crypto: Initial implementation of Ascon-Hash256 kernel test robot
2025-12-20 16:20 ` kernel test robot
2025-12-22 17:41 ` 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=202512160656.DWMVkABi-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rusydi.makarim@kriptograf.id \
/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;
as well as URLs for NNTP newsgroup(s).