[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250225133153.64ea6687@gandalf.local.home>
Date: Tue, 25 Feb 2025 13:31:53 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Arnd Bergmann <arnd@...nel.org>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Mark Rutland <mark.rutland@....com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Joel Granados <joel.granados@...nel.org>,
Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH] ftrace: don't call kaslr_offset()
On Tue, 25 Feb 2025 10:00:58 +0100
Arnd Bergmann <arnd@...nel.org> wrote:
> From: Arnd Bergmann <arnd@...db.de>
>
> The kaslr_offset() function is only defined on architectures
> that implement CONFIG_RANDOMIZE_BASE, which leads to a
> build failure on 32-bit arm and likely others.
>
> Hide the function call behind an #ifdef.
>
> Fixes: ef378c3b8233 ("scripts/sorttable: Zero out weak functions in mcount_loc table")
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
> There is probably a nicer way to do this, this version was the
> minimum fix I found to unbreak the build.
Yep, I ended up removing the reference to kasrl_offset() altogether.
You are Cc'd on the new patch set.
Thanks,
-- Steve
> ---
> kernel/trace/ftrace.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Powered by blists - more mailing lists