Re: [PATCH v3] ftrace: Hide a extra entry in stack trace

[Steven Rostedt]

On Thu, 3 Oct 2024 00:28:28 +0900
Tatsuya S <tatsuya.s2862@xxxxxxxxx> wrote:

> > Tatsuya S <tatsuya.s2862@xxxxxxxxx> wrote:
> >   
> >> A extra entry is shown on stack trace(CONFIG_UNWINDER_ORC=y).
> >>
> >> [003] .....   110.171589: vfs_write <-__x64_sys_write
> >> [003] .....   110.171600: <stack trace>  
> >> => XXXXXXXXX (Wrong function name)  
> > 
> > BTW, instead of X'ing it out, can you show what that extra function was.
> > Just saying "Wrong function name" doesn't give me any idea of what happened.  
> This is changed each shutdown.
> For example, client_init_data, hidpp_driver_init, rfcomm_init.
> 
> The same function name was displayed each time if system was not shutdown.
> 
> And I added "nokaslr" to the kernel command line and boot, got same result.

So I'm trying to understand this part. Where is the function coming from
then? The skip is there to skip over the functions that are calling the
stack trace. It shouldn't be garbage, as the stack walk shouldn't be giving
us that.

Now I'm even more curious to what is going wrong.

-- Steve