U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Jonathan Humphreys <j-humphreys@ti.com>,
	Raymond Mao <raymond.mao@linaro.org>,
	Caleb Connolly <caleb.connolly@linaro.org>,
	Adriano Cordova <adrianox@gmail.com>,
	Michal Simek <michal.simek@amd.com>, Udit Kumar <u-kumar1@ti.com>,
	Simon Glass <sjg@chromium.org>, Devarsh Thakkar <devarsht@ti.com>,
	Hari Nagalla <hnagalla@ti.com>,
	Manorit Chawdhry <m-chawdhry@ti.com>,
	Santhosh Kumar K <s-k6@ti.com>,
	Neha Malcom Francis <n-francis@ti.com>,
	Daniel Schultz <d.schultz@phytec.de>,
	Viacheslav Bocharov <adeep@lexina.in>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Aashvij Shenai <a-shenai@ti.com>,
	Roger Quadros <rogerq@kernel.org>,
	Jonathan Humphreys <j-humphreys@ti.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Apurva Nandan <a-nandan@ti.com>, Bryan Brattlof <bb@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Wadim Egorov <w.egorov@phytec.de>, Tom Rini <trini@konsulko.com>,
	Robert Nelson <robertcnelson@gmail.com>,
	Nishanth Menon <nm@ti.com>,
	Sughosh Ganu <sughosh.ganu@linaro.org>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	Lukasz Majewski <lukma@denx.de>,
	s-vadapalli@ti.com
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] efi_firmware: set EFI capsule dfu_alt_info env explicitly
Date: Tue, 04 Feb 2025 15:13:51 +0100	[thread overview]
Message-ID: <87wme5kdb4.fsf@baylibre.com> (raw)
In-Reply-To: <20250203215351.2840144-2-j-humphreys@ti.com>

Hi Jon,

Thank you for the patch.

On lun., févr. 03, 2025 at 15:53, Jonathan Humphreys <j-humphreys@ti.com> wrote:

> The current implementation of EFI capsule update uses set_dfu_alt_info() to
> set the dfu_alt_info environment variable with the settings it requires.
> However, set_dfu_alt_info() is doing this for all DFU operations, even
> those unrelated to capsule update.
>
> Thus other uses of DFU, such as DFU boot which sets its own value for the
> dfu_alt_info environment variable, will have that setting overwritten with
> the capsule update setting. Similarly, any user defined value for the
> dfu_alt_info environment variable would get overwritten when any DFU
> operation was performed, including simply performing a "dfu 0 list"
> command.
>
> The solution is stop using the set_dfu_alt_info() mechanism to set the
> dfu_alt_info environment variable and instead explicitly set it to the
> capsule update's setting just before performing the capsule update's DFU
> operation, and then restore the environment variable back to its original
> value.
>
> This patch implements the explicit setting and restoring of the
> dfu_alt_info environment variable as part of the EFI capsule update
> operation.
>
> The fix is fully implemented in a subsequent patch that removes the capsule
> update dfu_alt_info support in set_dfu_alt_info().
>
> Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com>
> ---
>  lib/efi_loader/efi_firmware.c | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
>
> diff --git a/lib/efi_loader/efi_firmware.c b/lib/efi_loader/efi_firmware.c
> index 5a754c9cd03..d8b6d34ccab 100644
> --- a/lib/efi_loader/efi_firmware.c
> +++ b/lib/efi_loader/efi_firmware.c
> @@ -649,8 +649,10 @@ efi_status_t EFIAPI efi_firmware_fit_set_image(
>  	efi_status_t (*progress)(efi_uintn_t completion),
>  	u16 **abort_reason)
>  {
> +	int ret;
>  	efi_status_t status;
>  	struct fmp_state state = { 0 };
> +	char *orig_dfu_env;
>  
>  	EFI_ENTRY("%p %d %p %zu %p %p %p\n", this, image_index, image,
>  		  image_size, vendor_code, progress, abort_reason);
> @@ -663,9 +665,22 @@ efi_status_t EFIAPI efi_firmware_fit_set_image(
>  	if (status != EFI_SUCCESS)
>  		return EFI_EXIT(status);
>  
> +	orig_dfu_env = env_get("dfu_alt_info");
> +	ret = env_set("dfu_alt_info", update_info.dfu_string);
> +	if (ret) {
> +		pr_err("unable to set env variable \"dfu_alt_info\"!\n");

I could not find any other usage of pr_err() in this file so I think
we should use the log_err() instead of pr_err() here.

> +		return -EINVAL;
> +	}
> +
>  	if (fit_update(image))

Should we restore to orig_dfu_env in case fit_update() fails?
If not, why not? Maybe we can state this in the commit message or in a
code comment?

>  		return EFI_EXIT(EFI_DEVICE_ERROR);
>  
> +	ret = env_set("dfu_alt_info", orig_dfu_env);
> +	if (ret) {
> +		pr_err("unable to set env variable \"dfu_alt_info\"!\n");

pr_err() -> log_err()

> +		return -EINVAL;
> +	}
> +
>  	efi_firmware_set_fmp_state_var(&state, image_index);
>  
>  	return EFI_EXIT(EFI_SUCCESS);
> @@ -717,6 +732,7 @@ efi_status_t EFIAPI efi_firmware_raw_set_image(
>  	u8 dfu_alt_num;
>  	efi_status_t status;
>  	struct fmp_state state = { 0 };
> +	char *orig_dfu_env;
>  
>  	EFI_ENTRY("%p %d %p %zu %p %p %p\n", this, image_index, image,
>  		  image_size, vendor_code, progress, abort_reason);
> @@ -747,10 +763,23 @@ efi_status_t EFIAPI efi_firmware_raw_set_image(
>  		}
>  	}
>  
> +	orig_dfu_env = env_get("dfu_alt_info");
> +	ret = env_set("dfu_alt_info", update_info.dfu_string);
> +	if (ret) {
> +		pr_err("unable to set env variable \"dfu_alt_info\"!\n");

pr_err() -> log_err()

> +		return -EINVAL;
> +	}
> +
>  	if (dfu_write_by_alt(dfu_alt_num, (void *)image, image_size,
>  			     NULL, NULL))
>  		return EFI_EXIT(EFI_DEVICE_ERROR);
>  
> +	ret = env_set("dfu_alt_info", orig_dfu_env);
> +	if (ret) {
> +		pr_err("unable to set env variable \"dfu_alt_info\"!\n");

pr_err() -> log_err()

> +		return -EINVAL;
> +	}
> +
>  	efi_firmware_set_fmp_state_var(&state, image_index);
>  
>  	return EFI_EXIT(EFI_SUCCESS);
> -- 
> 2.34.1

  reply	other threads:[~2025-02-05  2:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 21:53 [PATCH 0/2] EFI Capsule update explicitly sets dfu_alt_info Jonathan Humphreys
2025-02-03 21:53 ` [PATCH 1/2] efi_firmware: set EFI capsule dfu_alt_info env explicitly Jonathan Humphreys
2025-02-04 14:13   ` Mattijs Korpershoek [this message]
2025-02-05  9:16   ` Ilias Apalodimas
2025-02-03 21:53 ` [PATCH 2/2] board: remove capsule update support in set_dfu_alt_info() Jonathan Humphreys
2025-02-04 14:18   ` Mattijs Korpershoek

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=87wme5kdb4.fsf@baylibre.com \
    --to=mkorpershoek@baylibre.com \
    --cc=a-nandan@ti.com \
    --cc=a-shenai@ti.com \
    --cc=adeep@lexina.in \
    --cc=adrianox@gmail.com \
    --cc=bb@ti.com \
    --cc=caleb.connolly@linaro.org \
    --cc=d.schultz@phytec.de \
    --cc=devarsht@ti.com \
    --cc=hnagalla@ti.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=j-humphreys@ti.com \
    --cc=lukma@denx.de \
    --cc=m-chawdhry@ti.com \
    --cc=michal.simek@amd.com \
    --cc=n-francis@ti.com \
    --cc=neil.armstrong@linaro.org \
    --cc=nm@ti.com \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=raymond.mao@linaro.org \
    --cc=robertcnelson@gmail.com \
    --cc=rogerq@kernel.org \
    --cc=s-k6@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=sjg@chromium.org \
    --cc=sughosh.ganu@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    --cc=w.egorov@phytec.de \
    --cc=xypron.glpk@gmx.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