mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] fs: efivarfs: allow creating variables under any GUID in loader mode
Date: Fri, 28 Aug 2026 14:52:05 +0200	[thread overview]
Message-ID: <178792152593.451404.2378757923178883522.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260826093720.2496298-1-a.fatoum@pengutronix.de>


On Wed, 26 Aug 2026 11:37:13 +0200, Ahmad Fatoum wrote:
> efivars_create() refuses to create variables outside the barebox vendor
> GUID. That dates from when barebox was only an EFI payload: on somebody
> else's firmware, whose NVRAM holds the platform's own state, a shell that
> can create Boot#### or BootOrder under the global GUID is a liability,
> and the payload only ever needs barebox-env-<guid> anyway.
> 
> The EFI loader took the same efivarfs over unchanged, where the argument
> does not hold. The store is barebox' own in-memory buffer backed by a
> file it writes itself, and everything the loader starts - the UEFI
> Shell, GRUB, the OS - can already create variables under any GUID. Only
> the barebox shell was held back:
> 
> [...]

Applied, thanks!

[1/1] fs: efivarfs: allow creating variables under any GUID in loader mode
      https://git.pengutronix.de/cgit/barebox/commit/?id=97f6cf9c5acb (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      reply	other threads:[~2026-08-28 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  9:37 Ahmad Fatoum
2026-08-28 12:52 ` Sascha Hauer [this message]

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=178792152593.451404.2378757923178883522.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@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