From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Stefan Kerkmann <s.kerkmann@pengutronix.de>
Subject: Re: [PATCH v2 0/7] arm: crypto: sha256: fix generation of thumb2 assembly
Date: Fri, 08 Nov 2024 10:52:11 +0100 [thread overview]
Message-ID: <173105953125.2295088.17383889318504713504.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241107-fix-sha256-assembly-v2-0-5fdb418f7f54@pengutronix.de>
On Thu, 07 Nov 2024 15:02:18 +0100, Stefan Kerkmann wrote:
> The checked in `sha256-core.S_shipped` assembly file has a thumb2
> specific workaround applied[1]. This fix wasn't backported to the perl
> script `sha256-armv4.pl` used to generate the assembly, thus when the
> script is run it would regenerate the buggy code.
>
> Under rare circumstances the modification timestamp of `sha256-armv4.pl`
> differs enough from `sha256-core.S_shipped` that make triggers a
> regeneration - leading to a broken sha256 digest on ARMv7 compiled in
> Thumb2 mode. In my case it was a Yocto build of barebox from an external
> source tree. Either the git checkout/clone process produced different
> timestamps, as these are non-deterministic, or I accidentally touched
> the file in another way. The bug expressed itself not in crashes but
> wrong sha256 sums.
>
> [...]
Applied, thanks!
[1/7] arm: crypto: sha256: fix generation of thumb2 assembly
https://git.pengutronix.de/cgit/barebox/commit/?id=636a00bd9a32 (link may not be stable)
[2/7] arm: configs: multi_v5_v6_defconfig: move rpi1 armv6 targets
https://git.pengutronix.de/cgit/barebox/commit/?id=506dc2607820 (link may not be stable)
[3/7] arm: configs: multi_v5_v6_defconfig: enable arm optimized sha1/sha256 digest
https://git.pengutronix.de/cgit/barebox/commit/?id=ea88325d8c6e (link may not be stable)
[4/7] arm: configs: multi_v7_defconfig: compile for thumb2
https://git.pengutronix.de/cgit/barebox/commit/?id=c48cade5d459 (link may not be stable)
[5/7] arm: configs: multi_v7_defconfig: enable arm optimized sha256 digest
https://git.pengutronix.de/cgit/barebox/commit/?id=e66a5d6f1d9b (link may not be stable)
[6/7] arm: configs: multi_v8_defconfig: enable arm optimized sha1/sha256 digest
https://git.pengutronix.de/cgit/barebox/commit/?id=8475ef42aa87 (link may not be stable)
[7/7] test: arm: rpi: run tests against multi_v5_v6_defconfig
https://git.pengutronix.de/cgit/barebox/commit/?id=8768361f59aa (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-11-08 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 14:02 Stefan Kerkmann
2024-11-07 14:02 ` [PATCH v2 1/7] " Stefan Kerkmann
2024-11-07 14:02 ` [PATCH v2 2/7] arm: configs: multi_v5_v6_defconfig: move rpi1 armv6 targets Stefan Kerkmann
2024-11-07 14:02 ` [PATCH v2 3/7] arm: configs: multi_v5_v6_defconfig: enable arm optimized sha1/sha256 digest Stefan Kerkmann
2024-11-07 14:02 ` [PATCH v2 4/7] arm: configs: multi_v7_defconfig: compile for thumb2 Stefan Kerkmann
2024-11-07 14:02 ` [PATCH v2 5/7] arm: configs: multi_v7_defconfig: enable arm optimized sha256 digest Stefan Kerkmann
2024-11-07 14:02 ` [PATCH v2 6/7] arm: configs: multi_v8_defconfig: enable arm optimized sha1/sha256 digest Stefan Kerkmann
2024-11-07 14:02 ` [PATCH v2 7/7] test: arm: rpi: run tests against multi_v5_v6_defconfig Stefan Kerkmann
2024-11-08 9:52 ` Sascha Hauer [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=173105953125.2295088.17383889318504713504.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.kerkmann@pengutronix.de \
/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