From: Ard Biesheuvel <ardb+git@google.com>
To: linux-kernel@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>, Kees Cook <kees@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kbuild@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: [PATCH v2 0/2] Simplify kallsyms offset table generation
Date: Fri, 16 Jan 2026 10:34:00 +0100 [thread overview]
Message-ID: <20260116093359.2442297-4-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
v2:
- implement minimal PC32 support for MIPS so it can tolerate the symbol
references emitted by kallsyms
- use signed decimal to represent the offset, so that symbols appearing
before _text can be represented correctly.
- add Kees's ack
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: Nicolas Schier <nsc@kernel.org>
Cc: Kees Cook <kees@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Kees Cook <kees@kernel.org>
Cc: linux-kbuild@vger.kernel.org
Cc: linux-hardening@vger.kernel.org
Cc: linux-mips@vger.kernel.org
Ard Biesheuvel (2):
mips: Add support for PC32 relocations in vmlinux
kallsyms: Get rid of kallsyms relative base
arch/mips/boot/tools/relocs.c | 2 +
arch/mips/include/asm/elf.h | 2 +
kernel/kallsyms.c | 6 +-
kernel/kallsyms_internal.h | 1 -
kernel/vmcore_info.c | 1 -
scripts/kallsyms.c | 64 ++++++--------------
scripts/link-vmlinux.sh | 4 ++
tools/perf/tests/vmlinux-kallsyms.c | 1 -
8 files changed, 29 insertions(+), 52 deletions(-)
--
2.52.0.457.g6b5491de43-goog
next reply other threads:[~2026-01-16 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 9:34 Ard Biesheuvel [this message]
2026-01-16 9:34 ` [PATCH v2 1/2] mips: Add support for PC32 relocations in vmlinux Ard Biesheuvel
2026-01-16 9:34 ` [PATCH v2 2/2] kallsyms: Get rid of kallsyms relative base Ard Biesheuvel
2026-01-30 0:10 ` [PATCH v2 0/2] Simplify kallsyms offset table generation Nathan Chancellor
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=20260116093359.2442297-4-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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