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 1/9] elf: Add relocation types used by nolibc
Date: Sat, 31 Jan 2026 16:44:32 +0900 [thread overview]
Message-ID: <20260131074440.732588-2-daniel@thingy.jp> (raw)
In-Reply-To: <20260131074440.732588-1-daniel@thingy.jp>
nolibc based programs are gaining the ability to relocate themselves
so that they can support PIE without needing a linker or special
crt from the toolchain.
Add the required relocation types.
Signed-off-by: Daniel Palmer <daniel@thingy.jp>
---
include/uapi/linux/elf-r.h | 27 +++++++++++++++++++++++++++
include/uapi/linux/elf.h | 1 +
2 files changed, 28 insertions(+)
create mode 100644 include/uapi/linux/elf-r.h
diff --git a/include/uapi/linux/elf-r.h b/include/uapi/linux/elf-r.h
new file mode 100644
index 000000000000..a1dce23104a7
--- /dev/null
+++ b/include/uapi/linux/elf-r.h
@@ -0,0 +1,27 @@
+/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
+#ifndef _LINUX_ELF_R_H
+#define _LINUX_ELF_R_H
+
+/* These constants define various ELF relocation types */
+#define R_386_RELATIVE 8
+
+#define R_68K_RELATIVE 22
+
+#define R_AARCH64_RELATIVE 1027
+
+#define R_AMD64_RELATIVE 8
+
+#define R_ARM_RELATIVE 23
+
+#define R_LARCH_RELATIVE 3
+
+#define R_PPC_RELATIVE 22
+
+#define R_RISCV_RELATIVE 3
+
+#define R_SH_RELATIVE 165
+
+#define R_SPARC_NONE 0
+#define R_SPARC_RELATIVE 22
+
+#endif /* _LINUX_ELF_R_H */
diff --git a/include/uapi/linux/elf.h b/include/uapi/linux/elf.h
index 819ded2d39de..3d18543d5460 100644
--- a/include/uapi/linux/elf.h
+++ b/include/uapi/linux/elf.h
@@ -4,6 +4,7 @@
#include <linux/types.h>
#include <linux/elf-em.h>
+#include <linux/elf-r.h>
/* 32-bit ELF base types. */
typedef __u32 Elf32_Addr;
--
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 ` Daniel Palmer [this message]
2026-02-01 16:25 ` [RFC PATCH 1/9] elf: Add relocation types used by nolibc 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 ` [RFC PATCH 9/9] fs/binfmt_elf_fdpic: Reflect that PIE binaries also work in KConfig help Daniel Palmer
2026-02-01 16:27 ` 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-2-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
Powered by JetHome