From: Daniel Palmer <daniel@thingy.jp>
To: linux@weissschuh.net, w@1wt.eu
Cc: kees@kernel.org, linux-kernel@vger.kernel.org,
Daniel Palmer <daniel@thingy.jp>
Subject: [RFC PATCH 9/9] fs/binfmt_elf_fdpic: Reflect that PIE binaries also work in KConfig help
Date: Sat, 31 Jan 2026 16:44:40 +0900 [thread overview]
Message-ID: <20260131074440.732588-10-daniel@thingy.jp> (raw)
In-Reply-To: <20260131074440.732588-1-daniel@thingy.jp>
Since commit 1bde925d2354 ("fs/binfmt_elf_fdpic.c: provide NOMMU loader for regular ELF binaries")
it has been possible to load some normal ELF binaries on nommu but it
wasn't documented in the help.
Since nolibc can generate static-pie binaries that work with this loader
document that normal ELFs can work as long as they are PIE and you have
a linker and that nolibc can also generate static-PIE binaries that
can load without any assitance.
Signed-off-by: Daniel Palmer <daniel@thingy.jp>
---
fs/Kconfig.binfmt | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/fs/Kconfig.binfmt b/fs/Kconfig.binfmt
index 1949e25c7741..71573bfd32ac 100644
--- a/fs/Kconfig.binfmt
+++ b/fs/Kconfig.binfmt
@@ -69,6 +69,16 @@ config BINFMT_ELF_FDPIC
It is also possible to run FDPIC ELF binaries on MMU linux also.
+ On nommu systems this can also load normal ELF binaries as long as
+ the binary is linked as PIE. If the binary is not static PIE, does not
+ include it's own relocation code, this requires a linker like uldso to
+ be present and set as the interpreter.
+
+ nolibc included in the kernel source can create static-PIE binaries
+ by including relocation code and the resulting binaries run on MMU
+ systems with the normal ELF loader and on nommu systems with this
+ loader.
+
config ELFCORE
bool
help
--
2.51.0
next prev parent reply other threads:[~2026-01-31 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 7:44 [RFC PATCH 0/9] nolibc: Add static-pie support Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 1/9] elf: Add relocation types used by nolibc Daniel Palmer
2026-02-01 16:25 ` Thomas Weißschuh
2026-01-31 7:44 ` [RFC PATCH 2/9] tools/nolibc: crt: Split _start_c() into stack-only and normal part Daniel Palmer
2026-02-01 16:33 ` Thomas Weißschuh
2026-01-31 7:44 ` [RFC PATCH 3/9] tools/nolibc: Add basic ELF self-relocation support for static PIE Daniel Palmer
2026-02-01 16:42 ` Thomas Weißschuh
2026-02-01 21:54 ` Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 4/9] tools/nolibc: m68k: Add relocation support Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 5/9] tools/nolibc: x86: Add relocation support for x86_64 Daniel Palmer
2026-02-01 17:56 ` Willy Tarreau
2026-01-31 7:44 ` [RFC PATCH 6/9] tools/nolibc: riscv: Add relocation support Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 7/9] tools/nolibc: arm: " Daniel Palmer
2026-01-31 7:44 ` [RFC PATCH 8/9] selftests/nolibc: Add option for building with -static-pie Daniel Palmer
2026-01-31 7:44 ` Daniel Palmer [this message]
2026-02-01 16:27 ` [RFC PATCH 9/9] fs/binfmt_elf_fdpic: Reflect that PIE binaries also work in KConfig help Thomas Weißschuh
2026-02-01 18:14 ` [RFC PATCH 0/9] nolibc: Add static-pie support Willy Tarreau
2026-02-01 21:45 ` Daniel Palmer
2026-02-01 21:49 ` Willy Tarreau
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=20260131074440.732588-10-daniel@thingy.jp \
--to=daniel@thingy.jp \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®