From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Chen, Rong A" <rong.a.chen@intel.com>,
kernel test robot <lkp@intel.com>,
"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: [PATCH] crypto: lib/blake2s - Split up test function to halve stack usage
Date: Tue, 20 Dec 2022 20:34:18 +0000 [thread overview]
Message-ID: <Y6IcSgmXpGwWP+xK@gmail.com> (raw)
In-Reply-To: <Y5V3JUL+r4k/XrL9@gondor.apana.org.au>
On Sun, Dec 11, 2022 at 02:22:29PM +0800, Herbert Xu wrote:
> On Thu, Dec 08, 2022 at 02:37:45PM +0800, Chen, Rong A wrote:
> >
> > 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=]
>
> Sorry, I didn't realise that you could still reproduce it. I tried
> reproducing it on multiple architectures and failed (all were in
> the 900 range).
>
> Anyhow, this patch reduces it by half for me so hopefully it should
> put this to rest.
>
> ---8<---
> Reduce the stack usage further by splitting up the test function.
>
> Also squash blocks and unaligned_blocks into one array.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> diff --git a/lib/crypto/blake2s-selftest.c b/lib/crypto/blake2s-selftest.c
> index 7d77dea15587..484b89332c83 100644
> --- a/lib/crypto/blake2s-selftest.c
> +++ b/lib/crypto/blake2s-selftest.c
> @@ -545,7 +545,7 @@ static const u8 blake2s_testvecs[][BLAKE2S_HASH_SIZE] __initconst = {
> 0xd6, 0x98, 0x6b, 0x07, 0x10, 0x65, 0x52, 0x65, },
> };
>
> -bool __init blake2s_selftest(void)
> +static bool __init blake2s_digest_test(void)
> {
> u8 key[BLAKE2S_KEY_SIZE];
> u8 buf[ARRAY_SIZE(blake2s_testvecs)];
> @@ -589,11 +589,20 @@ bool __init blake2s_selftest(void)
> }
> }
>
> + return success;
> +}
> +
> +static bool __init blake2s_random_test(void)
> +{
> + struct blake2s_state state;
> + bool success = true;
> + int i, l;
> +
Shouldn't these functions have 'noinline_for_stack' added to them?
- Eric
next prev parent reply other threads:[~2022-12-20 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 13:18 lib/crypto/blake2s-selftest.c:632:1: warning: the frame size of 1120 bytes is larger than 1024 bytes kernel test robot
2022-12-08 4:18 ` Herbert Xu
2022-12-08 6:37 ` Chen, Rong A
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 [this message]
2022-12-21 6:58 ` [v2 PATCH] " Herbert Xu
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=Y6IcSgmXpGwWP+xK@gmail.com \
--to=ebiggers@kernel.org \
--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=rong.a.chen@intel.com \
--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