[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABCJKudMzRcgZCVv4gF3QwKGxq3F2aVQj87WkMdh1ZFvy10DoQ@mail.gmail.com>
Date: Wed, 26 Oct 2022 08:36:29 -0700
From: Sami Tolvanen <samitolvanen@...gle.com>
To: kernel test robot <lkp@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>, llvm@...ts.linux.dev,
kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Kees Cook <keescook@...omium.org>
Subject: Re: ld.lld: error: undefined symbol: __kcfi_typeid_ftrace_stub_graph
On Tue, Oct 25, 2022 at 1:22 AM kernel test robot <lkp@...el.com> wrote:
> >> ld.lld: error: undefined symbol: __kcfi_typeid_ftrace_stub_graph
> >>> referenced by entry-ftrace.S:299 (arch/arm64/kernel/entry-ftrace.S:299)
> >>> arch/arm64/kernel/entry-ftrace.o:(.text+0x48) in archive vmlinux.a
We don't seem to have any C translation units that would take the
address of ftrace_stub_graph with this config, which means the
compiler won't generate the __kcfi_typeid_ftrace_stub_graph symbol.
Adding __ADDRESSABLE(ftrace_stub_graph) to a suitable place would fix
this issue, perhaps somewhere in arch/arm64/kernel/ftrace.c?
Sami
Powered by blists - more mailing lists