From: kernel test robot <lkp@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: crypto/ahash.c:1073:1: warning: the frame size of 1040 bytes is larger than 1024 bytes
Date: Sat, 22 Aug 2026 04:54:13 +0800 [thread overview]
Message-ID: <202608220456.HAcVMI5V-lkp@intel.com> (raw)
Hi Herbert,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 818bebeb63dd6bf5f4e07e145f6cdbace520a34c
commit: 9d9b193ed73a65ec47cf1fd39925b09da8216461 crypto: hash - Increase HASH_MAX_DESCSIZE for hmac(sha3-224-s390)
date: 1 year, 1 month ago
config: mips-eyeq5_defconfig (https://download.01.org/0day-ci/archive/20260822/202608220456.HAcVMI5V-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260822/202608220456.HAcVMI5V-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
| Fixes: 9d9b193ed73a ("crypto: hash - Increase HASH_MAX_DESCSIZE for hmac(sha3-224-s390)")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608220456.HAcVMI5V-lkp@intel.com/
All warnings (new ones prefixed by >>):
crypto/ahash.c: In function 'crypto_hash_digest':
>> crypto/ahash.c:1073:1: warning: the frame size of 1040 bytes is larger than 1024 bytes [-Wframe-larger-than=]
1073 | }
| ^
vim +1073 crypto/ahash.c
04bfa4c7d5119c Herbert Xu 2025-04-12 1059
04bfa4c7d5119c Herbert Xu 2025-04-12 1060 int crypto_hash_digest(struct crypto_ahash *tfm, const u8 *data,
04bfa4c7d5119c Herbert Xu 2025-04-12 1061 unsigned int len, u8 *out)
04bfa4c7d5119c Herbert Xu 2025-04-12 1062 {
19da081a28c95f Herbert Xu 2025-04-23 1063 HASH_REQUEST_ON_STACK(req, crypto_ahash_fb(tfm));
04bfa4c7d5119c Herbert Xu 2025-04-12 1064 int err;
04bfa4c7d5119c Herbert Xu 2025-04-12 1065
04bfa4c7d5119c Herbert Xu 2025-04-12 1066 ahash_request_set_callback(req, 0, NULL, NULL);
04bfa4c7d5119c Herbert Xu 2025-04-12 1067 ahash_request_set_virt(req, data, out, len);
04bfa4c7d5119c Herbert Xu 2025-04-12 1068 err = crypto_ahash_digest(req);
04bfa4c7d5119c Herbert Xu 2025-04-12 1069
04bfa4c7d5119c Herbert Xu 2025-04-12 1070 ahash_request_zero(req);
04bfa4c7d5119c Herbert Xu 2025-04-12 1071
04bfa4c7d5119c Herbert Xu 2025-04-12 1072 return err;
04bfa4c7d5119c Herbert Xu 2025-04-12 @1073 }
04bfa4c7d5119c Herbert Xu 2025-04-12 1074 EXPORT_SYMBOL_GPL(crypto_hash_digest);
04bfa4c7d5119c Herbert Xu 2025-04-12 1075
:::::: The code at line 1073 was first introduced by commit
:::::: 04bfa4c7d5119ca38f8133bfdae7957a60c8b221 crypto: hash - Add HASH_REQUEST_ON_STACK
:::::: TO: Herbert Xu <herbert@gondor.apana.org.au>
:::::: CC: Herbert Xu <herbert@gondor.apana.org.au>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-08-21 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 20:54 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-09 17:06 crypto/ahash.c:1073:1: warning: the frame size of 1040 bytes is larger than 1024 bytes kernel test robot
2026-05-11 6:42 ` Geert Uytterhoeven
2026-05-19 14:54 ` Christophe Leroy (CS GROUP)
2026-01-27 7:11 kernel test robot
2025-12-26 21:01 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=202608220456.HAcVMI5V-lkp@intel.com \
--to=lkp@intel.com \
--cc=herbert@gondor.apana.org.au \
--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;
as well as URLs for NNTP newsgroup(s).