From: Ard Biesheuvel <ardb+git@google.com>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Huacai Chen <chenhuacai@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: [PATCH v2 0/2] Handle .data.rel.ro correctly and use it for BPF
Date: Wed, 19 Feb 2025 11:55:43 +0100 [thread overview]
Message-ID: <20250219105542.2418786-4-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
LoongArch uses PIE codegen for the entire kernel, which has some
implications for how .rodata is populated and emitted into vmlinux.
Changes since v1: [0]
- Always use .data.rel.ro.c_jump_table for C jump tables
- Add Tiezhu Yang's Tested-by
- Split into two patches and rebase onto Linus's tree
[0] https://lore.kernel.org/all/20250218092538.1903204-2-ardb+git@google.com/T/#u
Cc: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>
Ard Biesheuvel (2):
asm-generic/vmlinux.lds: Move .data.rel.ro input into .rodata segment
objtool: Use fPIE compatible ELF sections for C jump tables
include/asm-generic/vmlinux.lds.h | 2 +-
include/linux/compiler.h | 2 +-
tools/objtool/check.c | 7 ++++---
tools/objtool/include/objtool/special.h | 2 +-
4 files changed, 7 insertions(+), 6 deletions(-)
--
2.48.1.601.g30ceb7b040-goog
next reply other threads:[~2025-02-19 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 10:55 Ard Biesheuvel [this message]
2025-02-19 10:55 ` [PATCH v2 1/2] asm-generic/vmlinux.lds: Move .data.rel.ro input into .rodata segment Ard Biesheuvel
2025-02-20 20:55 ` Josh Poimboeuf
2025-02-20 22:33 ` Ard Biesheuvel
2025-02-19 10:55 ` [PATCH v2 2/2] objtool: Use fPIE compatible ELF sections for C jump tables Ard Biesheuvel
2025-02-20 21:25 ` Josh Poimboeuf
2025-02-20 21:27 ` Josh Poimboeuf
2025-02-20 22:45 ` Ard Biesheuvel
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=20250219105542.2418786-4-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
--cc=yangtiezhu@loongson.cn \
/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®