From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/5] boot: implement devboot in C
Date: Fri, 30 Oct 2026 15:13:27 +0100 [thread overview]
Message-ID: <20261030-devboot-v1-0-ab9dd3a92c66@pengutronix.de> (raw)
devboot is a script on top of the boot command, which makes it hard to
integrate: Kernel command line fragments need a dedicated namespace to be
removed again, and booting with devboot by default needs a special boot
target. Also, boot overrides get lost when a boot script calls boot or
bootm itself.
This series hands overrides on to whatever a boot entry boots and turns
devboot into what it really is, an option to the boot command: boot -D,
or global.boot.devboot=1 to enable it by default. The devboot command
remains as a shorthand for boot -D.
The series is based on the "boot: UAF and double free fixes", "Add and
use file_exists() helper" and "boot: revert boot related globalvars after
booting" series.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (5):
boot: report the exit status of failing boot scripts
hush: export source_script()
boot: hand overrides on to nested boots and the bootm command
boot: implement devboot in C
sandbox: defconfig: enable boot overrides and devboot
Documentation/user/devboot.rst | 76 +++++++-----
arch/sandbox/configs/sandbox_defconfig | 2 +
commands/boot.c | 28 ++++-
commands/bootm.c | 3 +-
common/Kconfig | 12 +-
common/Makefile | 1 +
common/boot.c | 63 ++++++----
common/bootchooser.c | 13 +-
common/bootm.c | 22 +++-
common/devboot.c | 197 ++++++++++++++++++++++++++++++
common/hush.c | 17 ++-
defaultenv/defaultenv-2-base/bin/devboot | 52 +-------
defaultenv/defaultenv-2-base/boot/devboot | 8 --
include/boot.h | 9 ++
include/bootchooser.h | 2 +-
include/bootm.h | 3 +
include/devboot.h | 31 +++++
include/shell.h | 8 ++
test/py/test_boot_overrides.py | 92 ++++++++++++++
test/py/test_boot_script.py | 13 ++
test/py/test_devboot.py | 131 ++++++++++++++++++++
21 files changed, 653 insertions(+), 130 deletions(-)
---
base-commit: e23fbb0ea940ba8b0f7f153297cb48c39fcbf41d
change-id: 20261030-devboot-af494560e196
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2026-10-30 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 14:13 Sascha Hauer [this message]
2026-10-30 14:13 ` [PATCH 1/5] boot: report the exit status of failing boot scripts Sascha Hauer
2026-10-30 14:13 ` [PATCH 2/5] hush: export source_script() Sascha Hauer
2026-10-30 14:13 ` [PATCH 3/5] boot: hand overrides on to nested boots and the bootm command Sascha Hauer
2026-10-30 14:13 ` [PATCH 4/5] boot: implement devboot in C Sascha Hauer
2026-10-30 14:13 ` [PATCH 5/5] sandbox: defconfig: enable boot overrides and devboot 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=20261030-devboot-v1-0-ab9dd3a92c66@pengutronix.de \
--to=s.hauer@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