From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Song Liu <song@kernel.org>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, jpoimboe@kernel.org,
jikos@kernel.org, mbenes@suse.cz, pmladek@suse.com,
joe.lawrence@redhat.com, nathan@kernel.org, morbo@google.com,
justinstitt@google.com, mcgrof@kernel.org,
thunder.leizhen@huawei.com, kees@kernel.org,
kernel-team@meta.com, mmaurer@google.com,
samitolvanen@google.com, mhiramat@kernel.org,
rostedt@goodmis.org
Subject: Re: [PATCH v3 0/2] Fix kallsyms with CONFIG_LTO_CLANG
Date: Tue, 13 Aug 2024 13:29:07 +0900 [thread overview]
Message-ID: <20240813132907.e6f392ec38bcc08e6796a014@kernel.org> (raw)
In-Reply-To: <20240807220513.3100483-1-song@kernel.org>
On Wed, 7 Aug 2024 15:05:11 -0700
Song Liu <song@kernel.org> wrote:
> With CONFIG_LTO_CLANG, the compiler/linker adds .llvm.<hash> suffix to
> local symbols to avoid duplications. Existing scripts/kallsyms sorts
> symbols without .llvm.<hash> suffix. However, this causes quite some
> issues later on. Some users of kallsyms, such as livepatch, have to match
> symbols exactly.
>
> Address this by sorting full symbols at build time, and let kallsyms
> lookup APIs to match the symbols exactly.
>
I've tested this series and confirmed it makes kprobes work with llvm suffixed
symbols.
/sys/kernel/tracing # echo "p c_start.llvm.8011538628216713357" >> kprobe_events
/sys/kernel/tracing # cat kprobe_events
p:kprobes/p_c_start_llvm_8011538628216713357_0 c_start.llvm.8011538628216713357
/sys/kernel/tracing # echo "p c_start" >> kprobe_events
/sys/kernel/tracing # cat kprobe_events
p:kprobes/p_c_start_llvm_8011538628216713357_0 c_start.llvm.8011538628216713357
p:kprobes/p_c_start_0 c_start
And ftrace too.
/sys/kernel/tracing # grep ^c_start available_filter_functions
c_start.llvm.8011538628216713357
c_start
c_start.llvm.17132674095431275852
Tested-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
for this series.
> Changes v2 => v3:
> 1. Remove the _without_suffix APIs, as kprobe will not use them.
> (Masami Hiramatsu)
>
> v2: https://lore.kernel.org/live-patching/20240802210836.2210140-1-song@kernel.org/T/#u
>
> Changes v1 => v2:
> 1. Update the APIs to remove all .XXX suffixes (v1 only removes .llvm.*).
> 2. Rename the APIs as *_without_suffix. (Masami Hiramatsu)
> 3. Fix another user from kprobe. (Masami Hiramatsu)
> 4. Add tests for the new APIs in kallsyms_selftests.
>
> v1: https://lore.kernel.org/live-patching/20240730005433.3559731-1-song@kernel.org/T/#u
>
> Song Liu (2):
> kallsyms: Do not cleanup .llvm.<hash> suffix before sorting symbols
> kallsyms: Match symbols exactly with CONFIG_LTO_CLANG
>
> kernel/kallsyms.c | 55 +++++---------------------------------
> kernel/kallsyms_selftest.c | 22 +--------------
> scripts/kallsyms.c | 31 ++-------------------
> scripts/link-vmlinux.sh | 4 ---
> 4 files changed, 9 insertions(+), 103 deletions(-)
>
> --
> 2.43.5
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-08-13 4:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 22:05 [PATCH v3 0/2] Fix kallsyms with CONFIG_LTO_CLANG Song Liu
2024-08-07 22:05 ` [PATCH v3 1/2] kallsyms: Do not cleanup .llvm.<hash> suffix before sorting symbols Song Liu
2024-08-13 21:15 ` Song Liu
2024-08-07 22:05 ` [PATCH v3 2/2] kallsyms: Match symbols exactly with CONFIG_LTO_CLANG Song Liu
2024-08-13 21:16 ` Song Liu
2024-08-12 16:21 ` [PATCH v3 0/2] Fix kallsyms " Song Liu
2024-08-12 16:57 ` Luis Chamberlain
2024-08-12 18:13 ` Song Liu
2024-08-15 16:05 ` Kees Cook
2024-08-15 16:09 ` Song Liu
2024-08-13 4:29 ` Masami Hiramatsu [this message]
2024-08-13 21:20 ` Song Liu
2024-08-13 21:55 ` Sami Tolvanen
2024-08-14 12:09 ` Petr Mladek
2024-08-15 16:34 ` Kees Cook
2024-08-30 13:57 ` Miroslav Benes
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=20240813132907.e6f392ec38bcc08e6796a014@kernel.org \
--to=mhiramat@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=mmaurer@google.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--cc=song@kernel.org \
--cc=thunder.leizhen@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).