From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/5] public_keys: make const
Date: Mon, 20 Oct 2025 13:30:57 +0200 [thread overview]
Message-ID: <20251020-public-keys-const-v1-0-301de7918b06@pengutronix.de> (raw)
We current have a struct list_head member in struct public_key which
prevents them from being put into the readonly data section.
Move the list_head out of struct public_key so we can make the compiled in
keys const. With this we can do some further cleanup by removing the key
duplication functions.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (5):
public-keys: ecdsa: remove list in ecdsa keys
public-keys: move list out of struct public_key
public-keys: rsa: allow struct public_key to be const
public-keys: rsa: remove unused functions
public-keys: make const
commands/keys.c | 3 ++-
common/image-fit.c | 4 +--
crypto/Kconfig | 1 +
crypto/ecdsa.c | 18 -------------
crypto/public-keys.c | 61 ++++++---------------------------------------
crypto/rsa.c | 33 ++++++++----------------
include/crypto/ecdsa.h | 12 ---------
include/crypto/public_key.h | 16 ++++++------
include/crypto/rsa.h | 12 ++-------
scripts/keytoc.c | 8 +++---
10 files changed, 37 insertions(+), 131 deletions(-)
---
base-commit: e8bf031f85acbd792e489c8f4ecbcb770dda16ef
change-id: 20251020-public-keys-const-cf2a3007e0a6
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2025-10-20 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 11:30 Sascha Hauer [this message]
2025-10-20 11:30 ` [PATCH 1/5] public-keys: ecdsa: remove list in ecdsa keys Sascha Hauer
2025-10-20 11:30 ` [PATCH 2/5] public-keys: move list out of struct public_key Sascha Hauer
2025-10-20 11:31 ` [PATCH 3/5] public-keys: rsa: allow struct public_key to be const Sascha Hauer
2025-10-20 11:31 ` [PATCH 4/5] public-keys: rsa: remove unused functions Sascha Hauer
2025-10-20 11:31 ` [PATCH 5/5] public-keys: make const Sascha Hauer
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=20251020-public-keys-const-v1-0-301de7918b06@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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