public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][scarthgap 11/14] wic: bootimg-efi: Support + symbol in filenames
Date: Wed, 23 Apr 2025 06:20:22 -0700	[thread overview]
Message-ID: <081fa0ebb33dbbfd0f6e8239690261c0a9dcdb2c.1745356684.git.steve@sakoman.com> (raw)
In-Reply-To: <cover.1745356684.git.steve@sakoman.com>

From: Igor Opaniuk <igor.opaniuk@foundries.io>

Allow the '+' symbol as a valid character in filenames listed in the
IMAGE_EFI_BOOT_FILES variable.

The '+' symbol might be used to support boot counting for boot entries,
as described in the UAPI Boot Loader Specification [1]:

The boot counting data is stored in the name of the boot loader entry.
A boot loader entry file name may contain a plus (+) followed by a
number. This may optionally be followed by a minus (-)
followed by a second number. The dot (.) and file name suffix
(conf or efi) must immediately follow.
Boot counting is enabled for entries which match this pattern.

Example:
IMAGE_EFI_BOOT_FILES:append = " entry.conf;loader/entries/entry+3.conf"

[1] https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting
Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 3f25822281eb9423ff86105eaebb0bed48663648)
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
---
 scripts/lib/wic/plugins/source/bootimg-efi.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/wic/plugins/source/bootimg-efi.py b/scripts/lib/wic/plugins/source/bootimg-efi.py
index 7cc5131541..37d07093f5 100644
--- a/scripts/lib/wic/plugins/source/bootimg-efi.py
+++ b/scripts/lib/wic/plugins/source/bootimg-efi.py
@@ -245,7 +245,7 @@ class BootimgEFIPlugin(SourcePlugin):
 
             # list of tuples (src_name, dst_name)
             deploy_files = []
-            for src_entry in re.findall(r'[\w;\-\./\*]+', boot_files):
+            for src_entry in re.findall(r'[\w;\-\.\+/\*]+', boot_files):
                 if ';' in src_entry:
                     dst_entry = tuple(src_entry.split(';'))
                     if not dst_entry[0] or not dst_entry[1]:
-- 
2.43.0



  parent reply	other threads:[~2025-04-23 13:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 13:20 [OE-core][scarthgap 00/14] Patch review Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 01/14] libsoup: Fix CVE-2025-32910 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 02/14] libsoup: Fix CVE-2025-32909 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 03/14] libsoup: Fix CVE-2025-32911 & CVE-2025-32913 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 04/14] libsoup: Fix CVE-2025-32912 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 05/14] libsoup: Fix CVE-2025-32906 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 06/14] binutils: patch CVE-2025-1182 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 07/14] sqlite3: patch CVE-2025-3277 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 08/14] sqlite3: patch CVE-2025-29088 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 09/14] curl: fix CVE-2024-11053 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 10/14] curl: fix CVE-2025-0167 Steve Sakoman
2025-04-23 13:20 ` Steve Sakoman [this message]
2025-04-23 13:20 ` [OE-core][scarthgap 12/14] systemd: upgrade 255.17 -> 255.18 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 13/14] python3-jinja2: upgrade 3.1.4 -> 3.1.6 Steve Sakoman
2025-04-23 13:20 ` [OE-core][scarthgap 14/14] bluez5: add missing tools to noinst-tools package Steve Sakoman

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=081fa0ebb33dbbfd0f6e8239690261c0a9dcdb2c.1745356684.git.steve@sakoman.com \
    --to=steve@sakoman.com \
    --cc=openembedded-core@lists.openembedded.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