From: Peng Fan <peng.fan@oss.nxp.com>
To: Abdelrahman Ibrahem <mail@aibrahem.com>
Cc: u-boot@lists.denx.de, Peng Fan <peng.fan@nxp.com>,
Simon Glass <sjg@chromium.org>, Stefano Babic <sbabic@denx.de>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] arm: imx: Remove arch_env_get_location to fix env lockdown
Date: Sun, 15 Dec 2024 09:05:18 +0800 [thread overview]
Message-ID: <20241215010518.GA16463@localhost.localdomain> (raw)
In-Reply-To: <20241107125122.48361-1-mail@aibrahem.com>
s/imx/layerscape/
On Thu, Nov 07, 2024 at 01:50:44PM +0100, Abdelrahman Ibrahem wrote:
>This patch resolves an issue encountered with Layerscape SoCs, where
>attempts to restrict write access to environment variables to enforce
>secureboot are ineffective when using the CONFIG_ENV_IS_NOWHERE
>configuration in combination with CONFIG_ENV_IS_IN_xxx.
>
>Signed-off-by: Abdelrahman Ibrahem <mail@aibrahem.com>
>---
>
> arch/arm/cpu/armv8/fsl-layerscape/cpu.c | 41 -------------------------
> 1 file changed, 41 deletions(-)
>
>diff --git a/arch/arm/cpu/armv8/fsl-layerscape/cpu.c b/arch/arm/cpu/armv8/fsl-layerscape/cpu.c
>index d2d3e346a3..7dd5f429bf 100644
>--- a/arch/arm/cpu/armv8/fsl-layerscape/cpu.c
>+++ b/arch/arm/cpu/armv8/fsl-layerscape/cpu.c
>@@ -819,47 +819,6 @@ int mmc_get_env_dev(void)
> }
> #endif
>
>-enum env_location arch_env_get_location(enum env_operation op, int prio)
>-{
This looks wrong to me. Drop the arch_env_get_location would break
other cases.
Thanks,
Peng
next prev parent reply other threads:[~2024-12-15 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 12:50 [PATCH] arm: imx: Remove arch_env_get_location to fix env lockdown Abdelrahman Ibrahem
2024-12-15 1:05 ` Peng Fan [this message]
2024-12-15 20:55 ` Abdelrahman Ibrahem
2024-12-16 8:56 ` Peng Fan
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=20241215010518.GA16463@localhost.localdomain \
--to=peng.fan@oss.nxp.com \
--cc=mail@aibrahem.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@denx.de \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.