[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <172373965417.621926.8551687004756195926.b4-ty@kernel.org>
Date: Thu, 15 Aug 2024 09:34:17 -0700
From: Kees Cook <kees@...nel.org>
To: live-patching@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
Song Liu <song@...nel.org>
Cc: Kees Cook <kees@...nel.org>,
jpoimboe@...nel.org,
jikos@...nel.org,
mbenes@...e.cz,
pmladek@...e.com,
joe.lawrence@...hat.com,
nathan@...nel.org,
morbo@...gle.com,
justinstitt@...gle.com,
mcgrof@...nel.org,
thunder.leizhen@...wei.com,
kernel-team@...a.com,
mmaurer@...gle.com,
samitolvanen@...gle.com,
mhiramat@...nel.org,
rostedt@...dmis.org
Subject: Re: [PATCH v3 0/2] Fix kallsyms with CONFIG_LTO_CLANG
On Wed, 07 Aug 2024 15:05:11 -0700, Song Liu 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.
>
> [...]
Applied to for-linus/hardening, thanks!
[1/2] kallsyms: Do not cleanup .llvm.<hash> suffix before sorting symbols
https://git.kernel.org/kees/c/020925ce9299
[2/2] kallsyms: Match symbols exactly with CONFIG_LTO_CLANG
https://git.kernel.org/kees/c/fb6a421fb615
Take care,
--
Kees Cook
Powered by blists - more mailing lists