From: Sascha Hauer <s.hauer@pengutronix.de>
To: Fabian Pflug <f.pflug@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/4] common: bootm: add policy to commandline
Date: Fri, 13 Mar 2026 14:36:11 +0100 [thread overview]
Message-ID: <abQSywI_nJlVD2dJ@pengutronix.de> (raw)
In-Reply-To: <20260312-v2026-02-0-topic-sconfig_console-v1-1-4c3fccafab1e@pengutronix.de>
On Thu, Mar 12, 2026 at 10:16:42AM +0100, Fabian Pflug wrote:
> If security policies are used, then the variable bootm.provide_policy
> can be set to automatically append the currently selected security
> policy to the kernel commandline with the prefix
> barebox.security.policy=
> This allows the the system to behave different based on the selected
> security policy.
>
> Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
> ---
> common/bootm.c | 23 +++++++++++++++++++++++
> include/bootm.h | 5 +++++
> 2 files changed, 28 insertions(+)
>
> diff --git a/common/bootm.c b/common/bootm.c
> index 6318509884..cd90aa81e1 100644
> --- a/common/bootm.c
> +++ b/common/bootm.c
> @@ -22,6 +22,7 @@
> #include <uncompress.h>
> #include <zero_page.h>
> #include <security/config.h>
> +#include <security/policy.h>
>
> static LIST_HEAD(handler_list);
> static struct sconfig_notifier_block sconfig_notifier;
> @@ -75,6 +76,7 @@ static int bootm_dryrun;
> static int bootm_earlycon;
> static int bootm_provide_machine_id;
> static int bootm_provide_hostname;
> +static int bootm_provide_policy;
> static int bootm_verbosity;
> static int bootm_efi_mode = BOOTM_EFI_AVAILABLE;
>
> @@ -97,6 +99,7 @@ void bootm_data_init_defaults(struct bootm_data *data)
> data->appendroot = bootm_appendroot;
> data->provide_machine_id = bootm_provide_machine_id;
> data->provide_hostname = bootm_provide_hostname;
> + data->provide_policy = bootm_provide_policy;
> data->verbose = bootm_verbosity;
> data->dryrun = bootm_dryrun;
> data->efi_boot = bootm_efi_mode;
> @@ -118,6 +121,7 @@ void bootm_data_restore_defaults(const struct bootm_data *data)
> bootm_appendroot = data->appendroot;
> bootm_provide_machine_id = data->provide_machine_id;
> bootm_provide_hostname = data->provide_hostname;
> + bootm_provide_policy = data->provide_policy;
> bootm_verbosity = data->verbose;
> bootm_dryrun = data->dryrun;
> bootm_efi_mode = data->efi_boot;
> @@ -712,6 +716,20 @@ int bootm_boot(struct bootm_data *bootm_data)
> free(hostname_bootarg);
> }
>
> + if (IS_ENABLED(CONFIG_SECURITY_POLICY) && bootm_data->provide_policy) {
> + char *policy_bootargs;
> +
> + if (!active_policy->name) {
Could active_policy be NULL here?
> + pr_err("Providing policy is enabled but policy has no name\n");
> + ret = -EINVAL;
> + goto err_out;
> + }
> +
> + policy_bootargs = basprintf("barebox.security.policy=%s", active_policy->name);
> + globalvar_add_simple("linux.bootargs.policy", policy_bootargs);
Should be linux.bootargs.dyn.policy to make sure it gets cleared after a
boot attempt.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-03-13 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 9:16 [PATCH 0/4] Add helper for security policies Fabian Pflug
2026-03-12 9:16 ` [PATCH 1/4] common: bootm: add policy to commandline Fabian Pflug
2026-03-13 13:36 ` Sascha Hauer [this message]
2026-03-13 14:26 ` Fabian Pflug
2026-03-13 14:30 ` Sascha Hauer
2026-03-12 9:16 ` [PATCH 2/4] security: policy: set active policy on boot Fabian Pflug
2026-03-12 9:16 ` [PATCH 3/4] security: configure pinctrl based on policy name Fabian Pflug
2026-03-12 9:16 ` [PATCH 4/4] security: kernel_pinctrl: fixup pinctrl in kernel dts Fabian Pflug
2026-03-13 14:10 ` 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=abQSywI_nJlVD2dJ@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@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