From: kernel test robot <lkp@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: lib/crypto/sm3.c:169:6: warning: stack frame size (1200) exceeds limit (1024) in 'sm3_block_generic'
Date: Tue, 24 Jun 2025 01:38:24 +0800 [thread overview]
Message-ID: <202506240133.iBttMRY7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 86731a2a651e58953fc949573895f2fa6d456841
commit: cb16ba46958e41f8d805cbdb027a601b3a0c65b4 crypto: lib/sm3 - Export generic block function
date: 10 weeks ago
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20250624/202506240133.iBttMRY7-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 875b36a8742437b95f623bab1e0332562c7b4b3f)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250624/202506240133.iBttMRY7-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/202506240133.iBttMRY7-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> lib/crypto/sm3.c:169:6: warning: stack frame size (1200) exceeds limit (1024) in 'sm3_block_generic' [-Wframe-larger-than]
169 | void sm3_block_generic(struct sm3_state *sctx, u8 const *data, int blocks)
| ^
1 warning generated.
vim +/sm3_block_generic +169 lib/crypto/sm3.c
168
> 169 void sm3_block_generic(struct sm3_state *sctx, u8 const *data, int blocks)
170 {
171 u32 W[16];
172
173 do {
174 sm3_transform(sctx, data, W);
175 data += SM3_BLOCK_SIZE;
176 } while (--blocks);
177
178 memzero_explicit(W, sizeof(W));
179 }
180 EXPORT_SYMBOL_GPL(sm3_block_generic);
181
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-23 17:38 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=202506240133.iBttMRY7-lkp@intel.com \
--to=lkp@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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
all inboxes | Powered by JetHome®