From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
kernel test robot <lkp@intel.com>
Cc: "Jason A. Donenfeld" <zx2c4@kernel.org>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: lib/crypto/blake2s-selftest.c:632:1: warning: the frame size of 1120 bytes is larger than 1024 bytes
Date: Thu, 8 Dec 2022 14:37:45 +0800 [thread overview]
Message-ID: <d25ac395-4335-be88-9dc5-364f5715554f@intel.com> (raw)
In-Reply-To: <Y5Flnb8jadyDebx3@gondor.apana.org.au>
On 12/8/2022 12:18 PM, Herbert Xu wrote:
> On Mon, Nov 07, 2022 at 09:18:05PM +0800, kernel test robot wrote:
>> Hi Jason,
>>
>> FYI, the error/warning still remains.
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: f0c4d9fc9cc9462659728d168387191387e903cc
>> commit: 2d16803c562ecc644803d42ba98a8e0aef9c014e crypto: blake2s - remove shash module
>> date: 5 months ago
>> config: i386-buildonly-randconfig-r006-20221107
>> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
>> reproduce (this is a W=1 build):
>> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2d16803c562ecc644803d42ba98a8e0aef9c014e
>> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> git fetch --no-tags linus master
>> git checkout 2d16803c562ecc644803d42ba98a8e0aef9c014e
>
> This was fixed months ago with
>
> commit d6c14da474bf260d73953fbf7992c98d9112aec7
> Author: Jason A. Donenfeld <Jason@zx2c4.com>
> Date: Mon Jun 20 09:52:43 2022 +0200
>
> crypto: lib/blake2s - reduce stack frame usage in self test
>
> Why is LKP still testing the old commit?
Hi Herbert,
Thanks for the information, I checked the result of the fix commit,
it reduced the stack frame but the warning still exists:
lib/crypto/blake2s-selftest.c:632:1: warning: the frame size of 1056
bytes is larger than 1024 bytes [-Wframe-larger-than=]
We'll ignore commit 2d16803c56 to avoid reporting it again.
Best Regards,
Rong Chen
>
> Cheers,
>
next prev parent reply other threads:[~2022-12-08 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 13:18 kernel test robot
2022-12-08 4:18 ` Herbert Xu
2022-12-08 6:37 ` Chen, Rong A [this message]
2022-12-11 6:22 ` [PATCH] crypto: lib/blake2s - Split up test function to halve stack usage Herbert Xu
2022-12-20 20:34 ` Eric Biggers
2022-12-21 6:58 ` [v2 PATCH] " Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2022-08-14 8:50 lib/crypto/blake2s-selftest.c:632:1: warning: the frame size of 1120 bytes is larger than 1024 bytes 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=d25ac395-4335-be88-9dc5-364f5715554f@intel.com \
--to=rong.a.chen@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zx2c4@kernel.org \
/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®