On Mon, Mar 2, 2026 at 12:16 AM Jiri Olsa <[email protected]> wrote: > > Ihor and Kumar reported splat from ftrace_get_addr_curr [1], which happened > because of the missing ftrace_lock in update_ftrace_direct_add/del functions > allowing concurrent access to ftrace internals. > > The ftrace_update_ops function must be guarded by ftrace_lock, adding that. > > Fixes: 05dc5e9c1fe1 ("ftrace: Add update_ftrace_direct_add function") > Fixes: 8d2c1233f371 ("ftrace: Add update_ftrace_direct_del function") > Reported-by: Ihor Solodrai <[email protected]> > Reported-by: Kumar Kartikeya Dwivedi <[email protected]> > Closes: > https://lore.kernel.org/bpf/[email protected]/ > Tested-by: Ihor Solodrai <[email protected]> > Signed-off-by: Jiri Olsa <[email protected]>
lgtm. Steven, should it land through ftrace tree?
