mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Thomas Bonnefille <thomas.bonnefille@bootlin.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"open list:BAREBOX" <barebox@lists.infradead.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Miquèl Raynal" <miquel.raynal@bootlin.com>,
	"Hervé Codina" <herve.codina@bootlin.com>
Subject: Re: [PATCH v2 3/3] FIT: add cmdline to whitelist of non-hashed properties
Date: Fri, 2 Oct 2026 12:58:01 +0200	[thread overview]
Message-ID: <d924d7df-d8e8-45ea-82b1-10795138a8dd@pengutronix.de> (raw)
In-Reply-To: <20260924-add-cmdline-fitimage-v2-3-4a665e165002@bootlin.com>

Hi,

On 9/24/26 19:59, Thomas Bonnefille wrote:
> The cmdline parameter of the fitimage is an additional optional property
> in a configuration node that is used to transmit information to the next
> bootstage.
> Just like description, compatible and default, this property doesn't
> reference an image (e.g. a kernel, a ramdisk or an fdt) and so it isn't
> hashed and shouldn't be added to the list of hashed images.

While the content of the patch is correct, this sentence isn't completely:
The property is being hashed (otherwise it would be a glaring security hole),
but it's not hashed as an image, meaning its content isn't resolved to a node.

I'll Cc you on an amend! commit to clarify this.

Thanks,
Ahmad

> Add `cmdline` to the whitelist of property in a configuration node that
> aren't images.
> 
> Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
> ---
>  common/image-fit.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/common/image-fit.c b/common/image-fit.c
> index 635f63c9e2..cd477911cc 100644
> --- a/common/image-fit.c
> +++ b/common/image-fit.c
> @@ -333,6 +333,7 @@ static int fit_config_build_hash_nodes(struct fit_handle *handle,
>  	for_each_property_of_node(conf_node, prop) {
>  		if (!strcmp(prop->name, "description") ||
>  		    !strcmp(prop->name, "compatible") ||
> +		    !strcmp(prop->name, "cmdline") ||
>  		    !strcmp(prop->name, "default"))
>  			continue;
>  
> 


-- 
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 |



  reply	other threads:[~2026-10-02 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 17:59 [PATCH v2 0/3] FIT: parse and use the cmdline property of FIT images Thomas Bonnefille
2026-09-24 17:59 ` [PATCH v2 1/3] bootm: add fitimage command line to bootargs Thomas Bonnefille
2026-09-24 17:59 ` [PATCH v2 2/3] test: py: add test for fit cmdline parameter Thomas Bonnefille
2026-09-24 17:59 ` [PATCH v2 3/3] FIT: add cmdline to whitelist of non-hashed properties Thomas Bonnefille
2026-10-02 10:58   ` Ahmad Fatoum [this message]
2026-10-01 20:32 ` [PATCH v2 0/3] FIT: parse and use the cmdline property of FIT images 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=d924d7df-d8e8-45ea-82b1-10795138a8dd@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=herve.codina@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=s.hauer@pengutronix.de \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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