From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] boot/shim: add patch to fix builds with -O3 / -Ofast
Date: Mon, 15 Jun 2026 22:54:26 +0200 [thread overview]
Message-ID: <1b28122fd20ea52b5d67f4fa4c353266@free.fr> (raw)
In-Reply-To: <20260615202534.1281579-1-peter@korsgaard.com>
On 15/06/2026 22:25, Peter Korsgaard wrote:
> Fixes:
> https://autobuild.buildroot.net/results/c6ad52a048ba030bb1adc3ee1aeb69ef880cbdad/
> https://autobuild.buildroot.net/results/136d1afc2ecacea6a4e12b915073e3eaf5c8ca01/
> https://autobuild.buildroot.net/results/a3f293371f6bd0125dc7baa5afb64373e4383f4f/
>
> Shim contains an embedded copy of OpenSSL. Depending on the
> optimization
> level, an error is triggered from make_kn():
>
> In function 'make_kn',
> inlined from 'make_kn' at crypto/cmac/cmac.c:81:13,
> inlined from 'CMAC_Init' at crypto/cmac/cmac.c:205:9:
> crypto/cmac/cmac.c:92:20: error: writing 1 byte into a region of size 0
> [-Werror=stringop-overflow=]
> 92 | k1[bl - 1] ^= bl == 16 ? 0x87 : 0x1b;
> | ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
> crypto/cmac/cmac.c: In function 'CMAC_Init':
> crypto/cmac/cmac.c:69:19: note: at offset 2147483647 into destination
> object 'k1' of size 32
> 69 | unsigned char k1[EVP_MAX_BLOCK_LENGTH];
> | ^~
>
> Fix it by including a patch submitted upstream which backports an
> upstream
> OpenSSL change to workaround this.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-06-15 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 20:25 [Buildroot] [PATCH] boot/shim: add patch to fix builds with -O3 / -Ofast Peter Korsgaard
2026-06-15 20:54 ` Julien Olivain via buildroot [this message]
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=1b28122fd20ea52b5d67f4fa4c353266@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=peter@korsgaard.com \
/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