linux-kernel - Re: ftrace bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220307082850.0278e961@gandalf.local.home>
Date:   Mon, 7 Mar 2022 08:28:50 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Arend van Spriel <arend.vanspriel@...adcom.com>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: ftrace bug

On Mon, 7 Mar 2022 13:00:05 +0100
Arend van Spriel <arend.vanspriel@...adcom.com> wrote:

> On 3/7/2022 12:26 PM, Arend van Spriel wrote:
> > Hi Steven,
> > 
> > I wanted to use FTRACE on an ARM platform and I hit the following 
> > warning which results in ftrace bug. This happens upon loading a module. 
> > Looking up the warning I suspect the branch target is too far off. The 
> > module is quite large and therefor not loaded in the modules section. Is 
> > there a way to exclude a module. In ftrace_module_init I see a check for 
> > !mod->num_ftrace_callsites. Is there a way to avoid creating ftrace 
> > callsites in a module?  
> 
> Could it be accomplished by this?
> 
> CFLAGS_REMOVE_lockdep.o = $(CC_FLAGS_FTRACE)
> 

You mean with something other than "lockdep.o".

You can do that to remove all ftrace callers from the .o file.

You could add the problem functions with "notrace" (which you should be
able to see what functions those were from the ftrace_bug output after the
"cut here").

You could keep an entire directory from having ftrace to it with:

ccflags-remove-$(CONFIG_FUNCTION_TRACER) += $(CC_FLAGS_FTRACE)

in the make file for that directory, and it will remove it totally.

But this should be considered a work around, by removing this, you lose all
the functionality you get with ftrace (tracing, ebpf attachments, and live
patching).

-- Steve