ftrace,bpf: Use single direct ops for bpf trampolines
Jiri Olsa
reviewerv5 cover ftrace,bpf: Use single direct ops for bpf trampolines
hi,
while poking the multi-tracing interface I ended up with just one ftrace_ops object to attach all trampolines.
This change allows to use less direct API calls during the attachment changes in the future code, so in effect speeding up the attachment.
In current code we get a speed up from using just a single ftrace_ops object.
- with current code:
Performance counter stats for 'bpftrace -e fentry:vmlinux:ksys_* {} -c true':
6,364,157,902 cycles:k
828,728,902 cycles:u
1,064,803,824 instructions:u # 1.28 insn per cycle
23,797,500,067 instructions:k # 3.74 insn per cycle 4.416004987 seconds time elapsed
0.164121000 seconds user
1.289550000 seconds sys- with the fix:
Performance counter stats for 'bpftrace -e fentry:vmlinux:ksys_* {} -c true':
6,535,857,905 cycles:k
810,809,429 cycles:u
1,064,594,027 instructions:u # 1.31 insn per cycle
23,962,552,894 instructions:k # 3.67 insn per cycle 1.666961239 seconds time elapsed
0.157412000 seconds user
1.283396000 seconds sysThe speedup seems to be related to the fact that with single ftrace_ops object we don't call ftrace_shutdown anymore (we use ftrace_update_ops instead) and we skip the synchronize rcu calls (each ~100ms) at the end of that function.
rfc: https://lore.kernel.org/bpf/[email protected]/ v1: https://lore.kernel.org/bpf/[email protected]/ v2: https://lore.kernel.org/bpf/[email protected]/ v3: https://lore.kernel.org/bpf/[email protected]/ v4: https://lore.kernel.org/bpf/[email protected]/
v5 changes:
- do not export ftrace_hash object [Steven]
- fix update_ftrace_direct_add new_filter_hash leak [ci]
v4 changes:
- rebased on top of bpf-next/master (with jmp attach changes) added patch 1 to deal with that
- added extra checks for update_ftrace_direct_del/mod to address the ci bot review
v3 changes:
- rebased on top of bpf-next/master
- fixed update_ftrace_direct_del cleanup path
- added missing inline to update_ftrace_direct_* stubs
v2 changes:
- rebased on top fo bpf-next/master plus Song's livepatch fixes [1]
- renamed the API functions [2] [Steven]
- do not export the new api [Steven]
- kept the original direct interface:
I'm not sure if we want to melt both *_ftrace_direct and the new interface into single one. It's bit different in semantic (hence the name change as Steven suggested [2]) and I don't think the changes are not that big so we could easily keep both APIs.
v1 changes:
- make the change x86 specific, after discussing with Mark options for arm64 [Mark]
thanks,
jirka
[1] https://lore.kernel.org/bpf/[email protected]/
[2] https://lore.kernel.org/bpf/[email protected]/
---
Jiri Olsa (9):
ftrace,bpf: Remove FTRACE_OPS_FL_JMP ftrace_ops flag
ftrace: Make alloc_and_copy_ftrace_hash direct friendly
ftrace: Export some of hash related functions
ftrace: Add update_ftrace_direct_add function
ftrace: Add update_ftrace_direct_del function
ftrace: Add update_ftrace_direct_mod function
bpf: Add trampoline ip hash table
ftrace: Factor ftrace_ops ops_func interface
bpf,x86: Use single ftrace_ops for direct calls
arch/x86/Kconfig | 1 + include/linux/bpf.h | 7 ++- include/linux/ftrace.h | 31 ++++++++++- kernel/bpf/trampoline.c | 234 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------- kernel/trace/Kconfig | 3 ++ kernel/trace/ftrace.c | 357 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------- 6 files changed, 560 insertions(+), 73 deletions(-)
Jiri Olsa
reviewerPATCH v5 1/9 ftrace,bpf: Remove FTRACE_OPS_FL_JMP ftrace_ops flag
At the moment the we allow the jmp attach only for ftrace_ops that has FTRACE_OPS_FL_JMP set. This conflicts with following changes where we use single ftrace_ops object for all direct call sites, so all could be be attached via just call or jmp.
We already limit the jmp attach support with config option and bit (LSB) set on the trampoline address. It turns out that's actually enough to limit the jmp attach for architecture and only for chosen addresses (with LSB bit set).
Each user of register_ftrace_direct or modify_ftrace_direct can set the trampoline bit (LSB) to indicate it has to be attached by jmp.
The bpf trampoline generation code uses trampoline flags to generate jmp-attach specific code and ftrace inner code uses the trampoline bit (LSB) to handle return from jmp attachment, so there's no harm to remove the FTRACE_OPS_FL_JMP bit.
The fexit/fmodret performance stays the same (did not drop), current code:
fentry : 77.904 ± 0.546M/s fexit : 62.430 ± 0.554M/s fmodret : 66.503 ± 0.902M/s
with this change:
fentry : 80.472 ± 0.061M/s fexit : 63.995 ± 0.127M/s fmodret : 67.362 ± 0.175M/s
--- include/linux/ftrace.h | 1 - kernel/bpf/trampoline.c | 32 ++++++++++++++------------------ kernel/trace/ftrace.c | 14 -------------- 3 files changed, 14 insertions(+), 33 deletions(-)
include/linux/ftrace.h +0 -1
@@ -359,7 +359,6 @@ enum {FTRACE_OPS_FL_DIRECT =BIT (17 ),FTRACE_OPS_FL_SUBOP =BIT (18 ), FTRACE_OPS_FL_GRAPH = BIT(19), - FTRACE_OPS_FL_JMP = BIT(20), };#ifndef CONFIG_DYNAMIC_FTRACE_WITH_ARGS
kernel/bpf/trampoline.c +14 -18
@@ -214,10 +214,15 @@ static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (lock_direct_mutex) - ret =modify_ftrace_direct (tr->fops, (long )new_addr); + ret =modify_ftrace_direct (tr->fops, addr);else - ret =modify_ftrace_direct_nolock (tr->fops, (long )new_addr); + ret =modify_ftrace_direct_nolock (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr, new_addr);
@@ -240,10 +245,15 @@ static int register_fentry(struct bpf_trampoline *tr, void *new_addr) }if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); + ret =ftrace_set_filter_ip (tr->fops, (unsigned long )ip,0 ,1 );if (ret)return ret; - ret =register_ftrace_direct (tr->fops, (long )new_addr); + ret =register_ftrace_direct (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr,0 ,NULL , new_addr); }
@@ -499,13 +509,6 @@ static int bpf_trampoline_update(struct bpf_trampoline *tr, bool lock_direct_mutif (err) goto out_free; -#ifdef CONFIG_DYNAMIC_FTRACE_WITH_JMP -if (bpf_trampoline_use_jmp (tr->flags)) - tr->fops->flags |=FTRACE_OPS_FL_JMP ; -else - tr->fops->flags &= ~FTRACE_OPS_FL_JMP ; -#endif -WARN_ON (tr->cur_image && total ==0 );if (tr->cur_image)/* progs already running at this address */
@@ -533,15 +536,8 @@ static int bpf_trampoline_update(struct bpf_trampoline *tr, bool lock_direct_mut tr->cur_image = im; out:/* If any error happens, restore previous flags */ -if (err) { +if (err) tr->flags = orig_flags; -#ifdef CONFIG_DYNAMIC_FTRACE_WITH_JMP -if (bpf_trampoline_use_jmp (tr->flags)) - tr->fops->flags |=FTRACE_OPS_FL_JMP ; -else - tr->fops->flags &= ~FTRACE_OPS_FL_JMP ; -#endif - }kfree (tlinks);return err;
kernel/trace/ftrace.c +0 -14
@@ -6017,15 +6017,8 @@ int register_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)if (ftrace_hash_empty (hash))return -EINVAL ; -/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; -mutex_lock (&direct_mutex); -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Make sure requested entries are not already registered.. */ size =1 << hash->size_bits;for (i =0 ; i < size; i++) {
@@ -6146,13 +6139,6 @@ __modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)lockdep_assert_held_once (&direct_mutex); -/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; - -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Enable the tmp_ops to have the same functions as the direct ops */ ftrace_ops_init (&tmp_ops); tmp_ops.func_hash = ops->func_hash;
Signature · 1 line
2.52.0
[email protected]
AI reviewRe: [PATCHv5 bpf-next 1/9] ftrace,bpf: Remove FTRACE_OPS_FL_JMP ftrace_ops flag
After this change, register_ftrace_direct() receives an address with the LSB bit already set (via ftrace_jmp_set) and stores it as-is in entry->direct. This address then flows through to…
Quoted 4 lines
include/linux/ftrace.h +0
-0
[ ... ]
Quoted 29 lines
kernel/bpf/trampoline.c +10
-2@@ -214,10 +214,15 @@ static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (lock_direct_mutex) - ret =modify_ftrace_direct (tr->fops, (long )new_addr); + ret =modify_ftrace_direct (tr->fops, addr);else - ret =modify_ftrace_direct_nolock (tr->fops, (long )new_addr); + ret =modify_ftrace_direct_nolock (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr, new_addr);@@ -240,10 +245,15 @@ static int register_fentry(struct bpf_trampoline *tr, void *new_addr) }if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags))
kernel/bpf/trampoline.c static int register_fentry(struct bpf_trampoline *tr, void *new_addr) · line 259
Quoted 10 lines
kernel/bpf/trampoline.c +3
-1+ addr =ftrace_jmp_set (addr); + ret =ftrace_set_filter_ip (tr->fops, (unsigned long )ip,0 ,1 );if (ret)return ret; - ret =register_ftrace_direct (tr->fops, (long )new_addr); + ret =register_ftrace_direct (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr,0 ,NULL , new_addr); }
After this change, register_ftrace_direct() receives an address with the LSB bit already set (via ftrace_jmp_set) and stores it as-is in entry->direct. This address then flows through to ftrace_find_rec_direct() which returns entry->direct unchanged.
In available_filter_functions_show():
direct = ftrace_find_rec_direct(rec->ip);
if (direct)
seq_printf(m, "\n\tdirect-->%pS", (void *)direct);Can the debug output show misleading symbol offsets? When the LSB is set, %pS will resolve addresses like "function+0x1" instead of just "function". This makes ftrace debug output harder to read for users trying to understand direct call attachments.
The fix would be to strip the LSB bit before printing:
seq_printf(m, "\n\tdirect-->%pS", (void *)ftrace_jmp_get(direct));
[ ... ]
Quoted 20 lines
kernel/trace/ftrace.c +0
-7@@ -6017,15 +6017,8 @@ int register_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)if (ftrace_hash_empty (hash))return -EINVAL ; -/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; -mutex_lock (&direct_mutex); -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Make sure requested entries are not already registered.. */ size =1 << hash->size_bits;for (i =0 ; i < size; i++) {
[ ... ]
Quoted 4 lines
kernel/trace/ftrace.c +0
-0@@ -6146,13 +6139,6 @@ __modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)lockdep_assert_held_once (&direct_mutex);
kernel/trace/ftrace.c __modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6144
Quoted 10 lines
kernel/trace/ftrace.c +0
-7-/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; - -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Enable the tmp_ops to have the same functions as the direct ops */ ftrace_ops_init (&tmp_ops); tmp_ops.func_hash = ops->func_hash;
[ ... ]
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/20247816064
Re: [PATCHv5 bpf-next 1/9] ftrace,bpf: Remove FTRACE_OPS_FL_JMP ftrace_ops flag
On 2025/12/16 05:31 [email protected] write:
Quoted 58 lines
Quoted 4 lines
include/linux/ftrace.h +0
-0[ ... ]
Quoted 29 lines
kernel/bpf/trampoline.c +10
-2@@ -214,10 +214,15 @@ static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (lock_direct_mutex) - ret =modify_ftrace_direct (tr->fops, (long )new_addr); + ret =modify_ftrace_direct (tr->fops, addr);else - ret =modify_ftrace_direct_nolock (tr->fops, (long )new_addr); + ret =modify_ftrace_direct_nolock (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr, new_addr);@@ -240,10 +245,15 @@ static int register_fentry(struct bpf_trampoline *tr, void *new_addr) }if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags))kernel/bpf/trampoline.c static int register_fentry(struct bpf_trampoline *tr, void *new_addr) · line 259
Quoted 10 lines
kernel/bpf/trampoline.c +3
-1+ addr =ftrace_jmp_set (addr); + ret =ftrace_set_filter_ip (tr->fops, (unsigned long )ip,0 ,1 );if (ret)return ret; - ret =register_ftrace_direct (tr->fops, (long )new_addr); + ret =register_ftrace_direct (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr,0 ,NULL , new_addr); }After this change,
register_ftrace_direct()receives an address with the LSB bit already set (viaftrace_jmp_set) and stores it as-is inentry->direct. This address then flows through toftrace_find_rec_direct()which returnsentry->directunchanged.In
available_filter_functions_show():direct = ftrace_find_rec_direct(rec->ip); if (direct) seq_printf(m, "\n\tdirect-->%pS", (void *)direct);
Quoted 7 lines
Can the debug output show misleading symbol offsets? When the LSB is set, %pS will resolve addresses like "
function+0x1" instead of just "function". This makes ftrace debug output harder to read for users trying to understand direct call attachments.The fix would be to strip the LSB bit before printing:
seq_printf(m, "\n\tdirect-->%pS", (void *)ftrace_jmp_get(direct));
Ah, this is a good point. However, it's totally another problem, and I'll follow up it.
Thanks!
Menglong Dong
Quoted 50 lines
[ ... ]
Quoted 20 lines
kernel/trace/ftrace.c +0
-7@@ -6017,15 +6017,8 @@ int register_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)if (ftrace_hash_empty (hash))return -EINVAL ; -/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; -mutex_lock (&direct_mutex); -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Make sure requested entries are not already registered.. */ size =1 << hash->size_bits;for (i =0 ; i < size; i++) {[ ... ]
Quoted 4 lines
kernel/trace/ftrace.c +0
-0@@ -6146,13 +6139,6 @@ __modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)lockdep_assert_held_once (&direct_mutex);kernel/trace/ftrace.c __modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6144
Quoted 10 lines
kernel/trace/ftrace.c +0
-7-/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; - -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Enable the tmp_ops to have the same functions as the direct ops */ ftrace_ops_init (&tmp_ops); tmp_ops.func_hash = ops->func_hash;[ ... ]
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.mdCI run summary: https://github.com/kernel-patches/bpf/actions/runs/20247816064
Re: [PATCHv5 bpf-next 1/9] ftrace,bpf: Remove FTRACE_OPS_FL_JMP ftrace_ops flag
In reply to [email protected]Quoted 52 lines · On Mon, Dec 15, 2025 at 09:31:51PM +0000, [email protected] wrote:
Quoted 4 lines
include/linux/ftrace.h +0
-0[ ... ]
Quoted 29 lines
kernel/bpf/trampoline.c +10
-2@@ -214,10 +214,15 @@ static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (lock_direct_mutex) - ret =modify_ftrace_direct (tr->fops, (long )new_addr); + ret =modify_ftrace_direct (tr->fops, addr);else - ret =modify_ftrace_direct_nolock (tr->fops, (long )new_addr); + ret =modify_ftrace_direct_nolock (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr, new_addr);@@ -240,10 +245,15 @@ static int register_fentry(struct bpf_trampoline *tr, void *new_addr) }if (tr->func.ftrace_managed) { +unsigned long addr = (unsigned long ) new_addr; + +if (bpf_trampoline_use_jmp (tr->flags))kernel/bpf/trampoline.c static int register_fentry(struct bpf_trampoline *tr, void *new_addr) · line 259
Quoted 10 lines
kernel/bpf/trampoline.c +3
-1+ addr =ftrace_jmp_set (addr); + ret =ftrace_set_filter_ip (tr->fops, (unsigned long )ip,0 ,1 );if (ret)return ret; - ret =register_ftrace_direct (tr->fops, (long )new_addr); + ret =register_ftrace_direct (tr->fops, addr); }else { ret =bpf_trampoline_update_fentry (tr,0 ,NULL , new_addr); }After this change,
register_ftrace_direct()receives an address with the LSB bit already set (viaftrace_jmp_set) and stores it as-is inentry->direct. This address then flows through toftrace_find_rec_direct()which returnsentry->directunchanged.
Quoted 1 line
In
available_filter_functions_show():
hum, there's no such function.. AFAICS it's t_show called through ftrace_avail_fops->ftrace_avail_open->show_ftrace_seq_ops
Quoted 5 lines
direct = ftrace_find_rec_direct(rec->ip);
if (direct)
seq_printf(m, "\n\tdirect-->%pS", (void *)direct);but yep, it's related problem, that Menglong said he will address in separate patch
thanks,
jirka
Quoted 56 lines
Can the debug output show misleading symbol offsets? When the LSB is set, %pS will resolve addresses like "
function+0x1" instead of just "function". This makes ftrace debug output harder to read for users trying to understand direct call attachments.The fix would be to strip the LSB bit before printing:
seq_printf(m, "\n\tdirect-->%pS", (void *)ftrace_jmp_get(direct));[ ... ]
Quoted 20 lines
kernel/trace/ftrace.c +0
-7@@ -6017,15 +6017,8 @@ int register_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)if (ftrace_hash_empty (hash))return -EINVAL ; -/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; -mutex_lock (&direct_mutex); -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Make sure requested entries are not already registered.. */ size =1 << hash->size_bits;for (i =0 ; i < size; i++) {[ ... ]
Quoted 4 lines
kernel/trace/ftrace.c +0
-0@@ -6146,13 +6139,6 @@ __modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)lockdep_assert_held_once (&direct_mutex);kernel/trace/ftrace.c __modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6144
Quoted 10 lines
kernel/trace/ftrace.c +0
-7-/* This is a "raw" address, and this should never happen. */ -if (WARN_ON_ONCE (ftrace_is_jmp (addr))) -return -EINVAL ; - -if (ops->flags &FTRACE_OPS_FL_JMP ) - addr =ftrace_jmp_set (addr); -/* Enable the tmp_ops to have the same functions as the direct ops */ ftrace_ops_init (&tmp_ops); tmp_ops.func_hash = ops->func_hash;[ ... ]
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.mdCI run summary: https://github.com/kernel-patches/bpf/actions/runs/20247816064
Jiri Olsa
reviewerPATCH v5 2/9 ftrace: Make alloc_and_copy_ftrace_hash direct friendly
In reply to Jiri OlsaMake alloc_and_copy_ftrace_hash to copy also direct address for each hash entry.
--- kernel/trace/ftrace.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
kernel/trace/ftrace.c +9 -2
@@ -1186,7 +1186,7 @@ static void __add_hash_entry(struct ftrace_hash *hash, }static struct ftrace_func_entry * -add_hash_entry (struct ftrace_hash *hash,unsigned long ip) +add_hash_entry_direct (struct ftrace_hash *hash,unsigned long ip,unsigned long direct) {struct ftrace_func_entry *entry;
@@ -1195,11 +1195,18 @@ add_hash_entry(struct ftrace_hash *hash, unsigned long ip)return NULL ; entry->ip = ip; + entry->direct = direct;__add_hash_entry (hash, entry);return entry; } +static struct ftrace_func_entry * +add_hash_entry (struct ftrace_hash *hash,unsigned long ip) +{ +return add_hash_entry_direct (hash, ip,0 ); +} +static void free_hash_entry (struct ftrace_hash *hash,struct ftrace_func_entry *entry)
@@ -1372,7 +1379,7 @@ alloc_and_copy_ftrace_hash(int size_bits, struct ftrace_hash *hash) size =1 << hash->size_bits;for (i =0 ; i < size; i++) {hlist_for_each_entry (entry, &hash->buckets[i], hlist) { -if (add_hash_entry (new_hash, entry->ip) ==NULL ) +if (add_hash_entry_direct (new_hash, entry->ip, entry->direct) ==NULL ) goto free_hash; } }
Signature · 1 line
2.52.0
Jiri Olsa
reviewerPATCH v5 3/9 ftrace: Export some of hash related functions
In reply to Jiri OlsaWe are going to use these functions in following changes.
--- include/linux/ftrace.h | 9 +++++++++ kernel/trace/ftrace.c | 7 +++---- 2 files changed, 12 insertions(+), 4 deletions(-)
include/linux/ftrace.h +9 -0
@@ -82,6 +82,7 @@ static inline void early_trace_init(void) { }struct module ;struct ftrace_hash ; +struct ftrace_func_entry ;#if defined(CONFIG_FUNCTION_TRACER ) && defined(CONFIG_MODULES ) && \ defined(CONFIG_DYNAMIC_FTRACE )
@@ -405,6 +406,14 @@ enum ftrace_ops_cmd {typedef int (*ftrace_ops_func_t )(struct ftrace_ops *op,enum ftrace_ops_cmd cmd); #ifdef CONFIG_DYNAMIC_FTRACE + +#define FTRACE_HASH_DEFAULT_BITS 10 + +struct ftrace_hash *alloc_ftrace_hash(int size_bits); +void free_ftrace_hash(struct ftrace_hash *hash); +struct ftrace_func_entry *add_hash_entry_direct(struct ftrace_hash *hash, + unsigned long ip, unsigned long direct); + /* The hash used to know what functions callbacks trace */ struct ftrace_ops_hash { struct ftrace_hash __rcu *notrace_hash;
kernel/trace/ftrace.c +3 -4
@@ -68,7 +68,6 @@ })/* hash bits for specific function selection */ -#define FTRACE_HASH_DEFAULT_BITS 10#define FTRACE_HASH_MAX_BITS 12#ifdef CONFIG_DYNAMIC_FTRACE
@@ -1185,7 +1184,7 @@ static void __add_hash_entry(struct ftrace_hash *hash, hash->count++; } -static struct ftrace_func_entry * +struct ftrace_func_entry *add_hash_entry_direct (struct ftrace_hash *hash,unsigned long ip,unsigned long direct) {struct ftrace_func_entry *entry;
@@ -1265,7 +1264,7 @@ static void clear_ftrace_mod_list(struct list_head *head)mutex_unlock (&ftrace_lock); } -static void free_ftrace_hash (struct ftrace_hash *hash) +void free_ftrace_hash (struct ftrace_hash *hash) {if (!hash || hash ==EMPTY_HASH )return ;
@@ -1305,7 +1304,7 @@ void ftrace_free_filter(struct ftrace_ops *ops) }EXPORT_SYMBOL_GPL (ftrace_free_filter); -static struct ftrace_hash *alloc_ftrace_hash (int size_bits) +struct ftrace_hash *alloc_ftrace_hash (int size_bits) {struct ftrace_hash *hash;int size;
Signature · 1 line
2.52.0
Re: [PATCHv5 bpf-next 3/9] ftrace: Export some of hash related functions
Quoted 12 lines · On Mon, 15 Dec 2025 22:13:56 +0100 Jiri Olsa <[email protected]> wrote:
index
505b7d3f5641..c0a72fcae1f6100644include/linux/ftrace.h +1
-0@@ -82,6 +82,7 @@ static inline void early_trace_init(void) { }struct module ;struct ftrace_hash ; +struct ftrace_func_entry ;#if defined(CONFIG_FUNCTION_TRACER ) && defined(CONFIG_MODULES ) && \ defined(CONFIG_DYNAMIC_FTRACE )
include/linux/ftrace.h enum ftrace_ops_cmd { · line 414
Quoted 9 lines
include/linux/ftrace.h +6
-0@@ -405,6 +406,14 @@ enum ftrace_ops_cmd {typedef int (*ftrace_ops_func_t )(struct ftrace_ops *op,enum ftrace_ops_cmd cmd);#ifdef CONFIG_DYNAMIC_FTRACE + +#define FTRACE_HASH_DEFAULT_BITS 10 + +struct ftrace_hash *alloc_ftrace_hash (int size_bits); +void free_ftrace_hash (struct ftrace_hash *hash); +struct ftrace_func_entry *add_hash_entry_direct(struct ftrace_hash *hash,
As this is no longer static and is exported to other users within the kernel, it should be renamed to: add_ftrace_hash_entry_direct() to keep the namespace unique.
-- Steve
Quoted 5 lines
include/linux/ftrace.h +2
-0+ unsigned long ip, unsigned long direct); +/* The hash used to know what functions callbacks trace */ struct ftrace_ops_hash {struct ftrace_hash __rcu *notrace_hash;
Re: [PATCHv5 bpf-next 3/9] ftrace: Export some of hash related functions
Quoted 17 lines · Steven Rostedt
Quoted 14 lines · On Mon, 15 Dec 2025 22:13:56 +0100 Jiri Olsa <[email protected]> wrote:
index
505b7d3f5641..c0a72fcae1f6100644include/linux/ftrace.h +1
-0@@ -82,6 +82,7 @@ static inline void early_trace_init(void) { }struct module ;struct ftrace_hash ; +struct ftrace_func_entry ;#if defined(CONFIG_FUNCTION_TRACER ) && defined(CONFIG_MODULES ) && \ defined(CONFIG_DYNAMIC_FTRACE )@@ -405,6 +406,14 @@ enum ftrace_ops_cmd {typedef int (*ftrace_ops_func_t )(struct ftrace_ops *op,enum ftrace_ops_cmd cmd);
Quoted 11 lines
include/linux/ftrace.h enum ftrace_ops_cmd { · line 414
Quoted 7 lines
include/linux/ftrace.h +6
-0#ifdef CONFIG_DYNAMIC_FTRACE + +#define FTRACE_HASH_DEFAULT_BITS 10 + +struct ftrace_hash *alloc_ftrace_hash (int size_bits); +void free_ftrace_hash (struct ftrace_hash *hash); +struct ftrace_func_entry *add_hash_entry_direct(struct ftrace_hash *hash,As this is no longer static and is exported to other users within the kernel, it should be renamed to:
add_ftrace_hash_entry_direct()to keep the namespace unique.
ok, will change
jirka
Quoted 8 lines
-- Steve
Quoted 5 lines
include/linux/ftrace.h +2
-0+ unsigned long ip, unsigned long direct); +/* The hash used to know what functions callbacks trace */ struct ftrace_ops_hash {struct ftrace_hash __rcu *notrace_hash;
Jiri Olsa
reviewerPATCH v5 4/9 ftrace: Add update_ftrace_direct_add function
In reply to Jiri OlsaAdding update_ftrace_direct_add function that adds all entries (ip -> addr) provided in hash argument to direct ftrace ops and updates its attachments.
The difference to current register_ftrace_direct is
- hash argument that allows to register multiple ip -> direct entries at once
- we can call update_ftrace_direct_add multiple times on the same ftrace_ops object, becase after first registration with register_ftrace_function_nolock, it uses ftrace_update_ops to update the ftrace_ops object
This change will allow us to have simple ftrace_ops for all bpf direct interface users in following changes.
--- include/linux/ftrace.h | 7 +++ kernel/trace/ftrace.c | 128 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 135 insertions(+)
include/linux/ftrace.h +7 -0
@@ -543,6 +543,8 @@ int unregister_ftrace_direct(struct ftrace_ops *ops, unsigned long addr,int modify_ftrace_direct (struct ftrace_ops *ops,unsigned long addr);int modify_ftrace_direct_nolock (struct ftrace_ops *ops,unsigned long addr); +int update_ftrace_direct_add (struct ftrace_ops *ops,struct ftrace_hash *hash); +void ftrace_stub_direct_tramp (void );#else
@@ -569,6 +571,11 @@ static inline int modify_ftrace_direct_nolock(struct ftrace_ops *ops, unsigned lreturn -ENODEV ; } +static inline int update_ftrace_direct_add (struct ftrace_ops *ops,struct ftrace_hash *hash) +{ +return -ENODEV ; +} +/* * This must be implemented by the architecture. * It is the way the ftrace direct_ops helper, when called
kernel/trace/ftrace.c +128 -0
134 lines not on this page · raw message
Signature · 1 line
2.52.0
kernel test robot
build botRe: [PATCHv5 bpf-next 4/9] ftrace: Add update_ftrace_direct_add function
kernel test robot noticed the following build warnings:
Hi Jiri,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Jiri-Olsa/ftrace-bpf-Remove-FTRACE_OPS_FL_JMP-ftrace_ops-flag/20251216-052916 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master patch link: https://lore.kernel.org/r/20251215211402.353056-5-jolsa%40kernel.org patch subject: [PATCHv5 bpf-next 4/9] ftrace: Add update_ftrace_direct_add function config: s390-randconfig-r122-20251216 (https://download.01.org/0day-ci/archive/20251216/[email protected]/config) compiler: s390-linux-gcc (GCC) 8.5.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251216/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
sparse warnings: (new ones prefixed by >>)
kernel/trace/ftrace.c:317:50: sparse: got struct ftrace_ops [noderef] __rcu **
kernel/trace/ftrace.c:324:12: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_ops * @@ got struct ftrace_ops [noderef] __rcu *next @@
kernel/trace/ftrace.c:324:12: sparse: expected struct ftrace_ops *
kernel/trace/ftrace.c:324:12: sparse: got struct ftrace_ops [noderef] __rcu *next
kernel/trace/ftrace.c:1067:43: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash * @@
kernel/trace/ftrace.c:1067:43: sparse: expected struct ftrace_hash [noderef] __rcu *notrace_hash
kernel/trace/ftrace.c:1067:43: sparse: got struct ftrace_hash *
kernel/trace/ftrace.c:1068:43: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash * @@
kernel/trace/ftrace.c:1068:43: sparse: expected struct ftrace_hash [noderef] __rcu *filter_hash
kernel/trace/ftrace.c:1068:43: sparse: got struct ftrace_hash *
kernel/trace/ftrace.c:1300:40: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@
kernel/trace/ftrace.c:1300:40: sparse: expected struct ftrace_hash *hash
kernel/trace/ftrace.c:1300:40: sparse: got struct ftrace_hash [noderef] __rcu *filter_hash
kernel/trace/ftrace.c:1301:40: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@
kernel/trace/ftrace.c:1301:40: sparse: expected struct ftrace_hash *hash
kernel/trace/ftrace.c:1301:40: sparse: got struct ftrace_hash [noderef] __rcu *notrace_hash
kernel/trace/ftrace.c:1302:37: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash * @@
kernel/trace/ftrace.c:1302:37: sparse: expected struct ftrace_hash [noderef] __rcu *filter_hash
kernel/trace/ftrace.c:1302:37: sparse: got struct ftrace_hash *
kernel/trace/ftrace.c:1303:38: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash * @@
kernel/trace/ftrace.c:1303:38: sparse: expected struct ftrace_hash [noderef] __rcu *notrace_hash
kernel/trace/ftrace.c:1303:38: sparse: got struct ftrace_hash *
kernel/trace/ftrace.c:2115:54: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash *old_hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@
kernel/trace/ftrace.c:2115:54: sparse: expected struct ftrace_hash *old_hash
kernel/trace/ftrace.c:2115:54: sparse: got struct ftrace_hash [noderef] __rcu *filter_hash
kernel/trace/ftrace.c:1507:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/trace/ftrace.c:1507:9: sparse: struct ftrace_hash [noderef] __rcu *
kernel/trace/ftrace.c:1507:9: sparse: struct ftrace_hash *
kernel/trace/ftrace.c:1523:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:1524:40: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:1525:40: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:1526:42: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:1697:18: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_ops *ops @@ got struct ftrace_ops [noderef] __rcu *[addressable] [toplevel] ftrace_ops_list @@ kernel/trace/ftrace.c:1698:43: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_ops *ops @@ got struct ftrace_ops [noderef] __rcu *next @@ kernel/trace/ftrace.c:1759:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:1760:22: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *notrace_hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:2093:50: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:2104:50: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:2587:53: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *static [toplevel] direct_functions @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:2598:36: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *static [toplevel] direct_functions @@ kernel/trace/ftrace.c:3394:51: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *B @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3395:66: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:3401:52: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *B @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3402:66: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:3415:41: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3416:51: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *src @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3419:52: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *notrace_hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3423:52: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *src @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3438:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3439:42: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3447:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3453:81: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3457:54: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *notrace_hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3459:56: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *new_hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3489:60: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *new_hash1 @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3490:49: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected struct ftrace_hash *new_hash2 @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3529:45: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3531:46: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3533:48: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3535:49: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3541:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3542:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3548:34: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *save_filter_hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3549:35: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *save_notrace_hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3551:45: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash *[addressable] filter_hash @@ kernel/trace/ftrace.c:3552:46: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash *[addressable] notrace_hash @@ kernel/trace/ftrace.c:3557:53: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash *save_filter_hash @@ kernel/trace/ftrace.c:3558:54: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash *save_notrace_hash @@ kernel/trace/ftrace.c:3605:31: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3606:32: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3621:59: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *[addressable] filter_hash @@ kernel/trace/ftrace.c:3622:59: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *[addressable] notrace_hash @@ kernel/trace/ftrace.c:3627:43: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *[addressable] filter_hash @@ kernel/trace/ftrace.c:3628:43: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *[addressable] notrace_hash @@ kernel/trace/ftrace.c:3630:39: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *[addressable] filter_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3631:40: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *[addressable] notrace_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3673:48: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3674:48: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:3675:45: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3676:46: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *notrace_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:3962:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:3979:22: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:4665:22: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:4668:22: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:5079:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:5081:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:5461:19: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:5605:19: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:5611:34: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash *[assigned] old_hash @@ kernel/trace/ftrace.c:5876:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:5878:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:5959:50: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *static [toplevel] direct_functions @@ kernel/trace/ftrace.c:5962:51: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *static [toplevel] direct_functions @@ kernel/trace/ftrace.c:5978:50: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:6022:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:6072:19: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *free_hash @@ got struct ftrace_hash [noderef] __rcu *static [toplevel] direct_functions @@ kernel/trace/ftrace.c:6137:50: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:6175:52: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *static [addressable] [assigned] [toplevel] direct_functions @@ kernel/trace/ftrace.c:6310:48: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *static [addressable] [assigned] [toplevel] direct_functions @@ kernel/trace/ftrace.c:6315:25: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *old_filter_hash @@ got struct ftrace_hash [noderef] __rcu * @@ >> kernel/trace/ftrace.c:6331:41: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *a @@ got struct ftrace_hash [noderef] __rcu *static [addressable] [assigned] [toplevel] direct_functions @@ kernel/trace/ftrace.c:6335:30: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *old_direct_functions @@ got struct ftrace_hash [noderef] __rcu *static [addressable] [assigned] [toplevel] direct_functions @@ kernel/trace/ftrace.c:6342:45: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash *[assigned] new_filter_hash @@ kernel/trace/ftrace.c:6347:53: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *filter_hash @@ got struct ftrace_hash *old_filter_hash @@ kernel/trace/ftrace.c:6630:35: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *extern [addressable] [toplevel] ftrace_graph_hash @@ got struct ftrace_hash *[assigned] hash @@ kernel/trace/ftrace.c:6632:43: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *extern [addressable] [toplevel] ftrace_graph_notrace_hash @@ got struct ftrace_hash *[assigned] hash @@ kernel/trace/ftrace.c:6701:35: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:6709:35: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash **orig_hash @@ got struct ftrace_hash [noderef] __rcu ** @@ kernel/trace/ftrace.c:6774:47: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *[addressable] [toplevel] ftrace_graph_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:6775:55: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct ftrace_hash [noderef] __rcu *[addressable] [toplevel] ftrace_graph_notrace_hash @@ got struct ftrace_hash * @@ kernel/trace/ftrace.c:7494:46: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:7495:47: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:7499:44: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:7517:18: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_ops *ops @@ got struct ftrace_ops [noderef] __rcu *[addressable] [toplevel] ftrace_ops_list @@ kernel/trace/ftrace.c:7517:66: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_ops *ops @@ got struct ftrace_ops [noderef] __rcu *next @@ kernel/trace/ftrace.c:7569:59: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:7570:59: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@ kernel/trace/ftrace.c:7959:62: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@ kernel/trace/ftrace.c:7960:62: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@
kernel/trace/ftrace.c:8004:36: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/trace/ftrace.c:8004:36: sparse: struct ftrace_ops [noderef] __rcu *
kernel/trace/ftrace.c:8004:36: sparse: struct ftrace_ops *
kernel/trace/ftrace.c:8780:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@
kernel/trace/ftrace.c:8780:14: sparse: expected struct ftrace_hash *hash
kernel/trace/ftrace.c:8780:14: sparse: got struct ftrace_hash [noderef] __rcu *filter_hash
kernel/trace/ftrace.c:8829:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@
kernel/trace/ftrace.c:8829:14: sparse: expected struct ftrace_hash *hash
kernel/trace/ftrace.c:8829:14: sparse: got struct ftrace_hash [noderef] __rcu *filter_hash
kernel/trace/ftrace.c:230:20: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:230:20: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:230:20: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3449:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3449:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3449:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3449:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3449:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3449:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3483:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3483:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3483:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3483:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3483:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:3483:29: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:6040:30: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:6049:21: sparse: sparse: dereference of noderef expression kernel/trace/ftrace.c:6051:17: sparse: sparse: dereference of noderef expression
kernel/trace/ftrace.c:3754:48: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *filter_hash @@
kernel/trace/ftrace.c:3754:48: sparse: expected struct ftrace_hash *hash
kernel/trace/ftrace.c:3754:48: sparse: got struct ftrace_hash [noderef] __rcu *filter_hash
kernel/trace/ftrace.c:3755:49: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct ftrace_hash *hash @@ got struct ftrace_hash [noderef] __rcu *notrace_hash @@
kernel/trace/ftrace.c:3755:49: sparse: expected struct ftrace_hash *hash
kernel/trace/ftrace.c:3755:49: sparse: got struct ftrace_hash [noderef] __rcu *notrace_hash
vim +6331 kernel/trace/ftrace.c
6292
6293 int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash)
6294 {
6295 struct ftrace_hash *old_direct_functions = NULL, *new_direct_functions;
6296 struct ftrace_hash *old_filter_hash, *new_filter_hash = NULL;
6297 struct ftrace_func_entry *entry;
6298 int i, size, err = -EINVAL;
6299 bool reg;
6300
6301 if (!hash_count(hash))
6302 return -EINVAL;
6303
6304 mutex_lock(&direct_mutex);
6305
6306 /* Make sure requested entries are not already registered. */
6307 size = 1 << hash->size_bits;
6308 for (i = 0; i < size; i++) {
6309 hlist_for_each_entry(entry, &hash->buckets[i], hlist) {
6310 if (__ftrace_lookup_ip(direct_functions, entry->ip))
6311 goto out_unlock;
6312 }
6313 }
6314
6315 old_filter_hash = ops->func_hash ? ops->func_hash->filter_hash : NULL;
6316
6317 /* If there's nothing in filter_hash we need to register the ops. */
6318 reg = hash_count(old_filter_hash) == 0;
6319 if (reg) {
6320 if (ops->func || ops->trampoline)
6321 goto out_unlock;
6322 if (ops->flags & FTRACE_OPS_FL_ENABLED)
6323 goto out_unlock;
6324 }
6325
6326 err = -ENOMEM;
6327 new_filter_hash = hash_add(old_filter_hash, hash);
6328 if (!new_filter_hash)
6329 goto out_unlock;
6330
> 6331 new_direct_functions = hash_add(direct_functions, hash);
6332 if (!new_direct_functions)
6333 goto out_unlock;
6334
6335 old_direct_functions = direct_functions;
6336 rcu_assign_pointer(direct_functions, new_direct_functions);
6337
6338 if (reg) {
6339 ops->func = call_direct_funcs;
6340 ops->flags |= MULTI_FLAGS;
6341 ops->trampoline = FTRACE_REGS_ADDR;
6342 ops->local_hash.filter_hash = new_filter_hash;
6343
6344 err = register_ftrace_function_nolock(ops);
6345 if (err) {
6346 /* restore old filter on error */
6347 ops->local_hash.filter_hash = old_filter_hash;
6348
6349 /* cleanup for possible another register call */
6350 ops->func = NULL;
6351 ops->trampoline = 0;
6352 } else {
6353 new_filter_hash = old_filter_hash;
6354 }
6355 } else {
6356 err = ftrace_update_ops(ops, new_filter_hash, EMPTY_HASH);
6357 /*
6358 * new_filter_hash is dup-ed, so we need to release it anyway,
6359 * old_filter_hash either stays on error or is already released
6360 */
6361 }
6362
6363 if (err) {
6364 /* reset direct_functions and free the new one */
6365 rcu_assign_pointer(direct_functions, old_direct_functions);
6366 old_direct_functions = new_direct_functions;
6367 }
6368
6369 out_unlock:
6370 mutex_unlock(&direct_mutex);
6371
6372 if (old_direct_functions && old_direct_functions != EMPTY_HASH)
6373 call_rcu_tasks(&old_direct_functions->rcu, register_ftrace_direct_cb);
6374 if (new_filter_hash)
6375 free_ftrace_hash(new_filter_hash);
6376
6377 return err;
6378 }
6379
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCHv5 bpf-next 4/9] ftrace: Add update_ftrace_direct_add function
In reply to Jiri OlsaQuoted 10 lines · On Mon, 15 Dec 2025 22:13:57 +0100 Jiri Olsa <[email protected]> wrote:
kernel/trace/ftrace.c +10
-0+/** +* hash_add - adds two struct ftrace_hash and returns the result +* @a: struct ftrace_hash object +* @b: struct ftrace_hash object +* +* Returns struct ftrace_hash object on success, NULL on error. +*/ +static struct ftrace_hash *hash_add (struct ftrace_hash *a,struct ftrace_hash *b) +{ +struct ftrace_func_entry *entry;
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6277
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+struct ftrace_hash *add; +int size, i; + + size =hash_count (a) +hash_count (b); +if (size >32 ) + size =32 ; + + add =alloc_and_copy_ftrace_hash (fls (size), a); +if (!add) + goto error;
You can just return NULL here, as add is NULL.
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6283
Quoted 6 lines
kernel/trace/ftrace.c +6
-0+ + size =1 << b->size_bits; +for (i =0 ; i < size; i++) { +hlist_for_each_entry (entry, &b->buckets[i], hlist) { +if (add_hash_entry_direct (add, entry->ip, entry->direct) ==NULL ) + goto error;
Could remove the error and have:
if (add_hash_entry_direct(add, entry->ip, entry->direct) == NULL) {
free_ftrace_hash(add);
return NULL;
}kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6292
Quoted 9 lines
kernel/trace/ftrace.c +9
-0+ } + } +return add; + + error: +free_ftrace_hash (add); +return NULL ; +} +
Non static functions require a kerneldoc header.
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6296
Quoted 4 lines
kernel/trace/ftrace.c +4
-0+int update_ftrace_direct_add (struct ftrace_ops *ops,struct ftrace_hash *hash) +{ +struct ftrace_hash *old_direct_functions =NULL , *new_direct_functions; +struct ftrace_hash *old_filter_hash, *new_filter_hash =NULL ;
BTW, I prefer to not double up on variables. That is to have each on their own lines. Makes it easier to read for me.
Review
Quoted 2 lines
(quoted diff) +2
-0+ struct ftrace_func_entry *entry; + int i, size, err = -EINVAL;
Even here.
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6308
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+bool reg; + +if (!hash_count (hash)) +return -EINVAL ; + +mutex_lock (&direct_mutex); + +/* Make sure requested entries are not already registered. */ + size =1 << hash->size_bits; +for (i =0 ; i < size; i++) {
If you want, you can remove the i declaration and use for(int i = 0; ... here.
Quoted 56 lines
kernel/trace/ftrace.c +56
-0+hlist_for_each_entry (entry, &hash->buckets[i], hlist) { +if (__ftrace_lookup_ip (direct_functions, entry->ip)) + goto out_unlock; + } + } + + old_filter_hash = ops->func_hash ? ops->func_hash->filter_hash :NULL ; + +/* If there's nothing in filter_hash we need to register the ops. */ + reg =hash_count (old_filter_hash) ==0 ; +if (reg) { +if (ops->func || ops->trampoline) + goto out_unlock; +if (ops->flags &FTRACE_OPS_FL_ENABLED ) + goto out_unlock; + } + + err = -ENOMEM ; + new_filter_hash =hash_add (old_filter_hash, hash); +if (!new_filter_hash) + goto out_unlock; + + new_direct_functions =hash_add (direct_functions, hash); +if (!new_direct_functions) + goto out_unlock; + + old_direct_functions = direct_functions; +rcu_assign_pointer (direct_functions, new_direct_functions); + +if (reg) { + ops->func = call_direct_funcs; + ops->flags |=MULTI_FLAGS ; + ops->trampoline =FTRACE_REGS_ADDR ; + ops->local_hash.filter_hash = new_filter_hash; + + err =register_ftrace_function_nolock (ops); +if (err) { +/* restore old filter on error */ + ops->local_hash.filter_hash = old_filter_hash; + +/* cleanup for possible another register call */ + ops->func =NULL ; + ops->trampoline =0 ; + }else { + new_filter_hash = old_filter_hash; + } + }else { + err =ftrace_update_ops (ops, new_filter_hash,EMPTY_HASH ); +/* +* new_filter_hash is dup-ed, so we need to release it anyway, +* old_filter_hash either stays on error or is already released +*/ + } + +if (err) { +/* reset direct_functions and free the new one */
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6374
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+rcu_assign_pointer (direct_functions, old_direct_functions); + old_direct_functions = new_direct_functions; + } + + out_unlock: +mutex_unlock (&direct_mutex); + +if (old_direct_functions && old_direct_functions !=EMPTY_HASH ) +call_rcu_tasks (&old_direct_functions->rcu, register_ftrace_direct_cb); +if (new_filter_hash)
free_ftrace_hash() checks for NULL, so you don't need the above if statement.
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6377
Quoted 3 lines
kernel/trace/ftrace.c +3
-0+free_ftrace_hash (new_filter_hash); + +return err;
-- Steve
Quoted 5 lines
kernel/trace/ftrace.c +2
-0+} +#endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */ /**
Re: [PATCHv5 bpf-next 4/9] ftrace: Add update_ftrace_direct_add function
Quoted 18 lines · Steven Rostedt
Quoted 14 lines · On Mon, 15 Dec 2025 22:13:57 +0100 Jiri Olsa <[email protected]> wrote:
kernel/trace/ftrace.c +14
-0+/** +* hash_add - adds two struct ftrace_hash and returns the result +* @a: struct ftrace_hash object +* @b: struct ftrace_hash object +* +* Returns struct ftrace_hash object on success, NULL on error. +*/ +static struct ftrace_hash *hash_add (struct ftrace_hash *a,struct ftrace_hash *b) +{ +struct ftrace_func_entry *entry; +struct ftrace_hash *add; +int size, i; + + size =hash_count (a) +hash_count (b);
Quoted 8 lines
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6277
Quoted 6 lines
kernel/trace/ftrace.c +6
-0+if (size >32 ) + size =32 ; + + add =alloc_and_copy_ftrace_hash (fls (size), a); +if (!add) + goto error;You can just return NULL here, as add is NULL.
ok
Quoted 10 lines
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6283
Quoted 7 lines
kernel/trace/ftrace.c +6
-0+ + size =1 << b->size_bits; +for (i =0 ; i < size; i++) { +hlist_for_each_entry (entry, &b->buckets[i], hlist) { +if (add_hash_entry_direct (add, entry->ip, entry->direct) ==NULL ) + goto error;Could remove the error and have:
Quoted 4 lines
if (add_hash_entry_direct(add, entry->ip, entry->direct) == NULL) {
free_ftrace_hash(add);
return NULL;
}ok
Quoted 13 lines
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6292
Quoted 11 lines
kernel/trace/ftrace.c +9
-0+ } + } +return add; + + error: +free_ftrace_hash (add); +return NULL ; +} +Non static functions require a kerneldoc header.
ah right, will add
Quoted 9 lines
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6296
Quoted 5 lines
kernel/trace/ftrace.c +4
-0+int update_ftrace_direct_add (struct ftrace_ops *ops,struct ftrace_hash *hash) +{ +struct ftrace_hash *old_direct_functions =NULL , *new_direct_functions; +struct ftrace_hash *old_filter_hash, *new_filter_hash =NULL ;BTW, I prefer to not double up on variables. That is to have each on their own lines. Makes it easier to read for me.
Quoted 4 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ struct ftrace_func_entry *entry; + int i, size, err = -EINVAL;Even here.
ok, will split
Quoted 13 lines
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6308
Quoted 11 lines
kernel/trace/ftrace.c +10
-0+bool reg; + +if (!hash_count (hash)) +return -EINVAL ; + +mutex_lock (&direct_mutex); + +/* Make sure requested entries are not already registered. */ + size =1 << hash->size_bits; +for (i =0 ; i < size; i++) {If you want, you can remove the i declaration and use for(int i = 0; ... here.
ok
SNIP
Quoted 8 lines
Quoted 8 lines
kernel/trace/ftrace.c +8
-0+ } + +if (err) { +/* reset direct_functions and free the new one */ +rcu_assign_pointer (direct_functions, old_direct_functions); + old_direct_functions = new_direct_functions; + } +
Quoted 8 lines
kernel/trace/ftrace.c int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr) · line 6374
Quoted 6 lines
+
out_unlock:kernel/trace/ftrace.c +5
-0+mutex_unlock (&direct_mutex); + +if (old_direct_functions && old_direct_functions !=EMPTY_HASH ) +call_rcu_tasks (&old_direct_functions->rcu, register_ftrace_direct_cb); +if (new_filter_hash)
free_ftrace_hash()checks for NULL, so you don't need the above if statement.
ok
thanks,
jirka
Jiri Olsa
reviewerPATCH v5 5/9 ftrace: Add update_ftrace_direct_del function
In reply to Jiri OlsaAdding update_ftrace_direct_del function that removes all entries (ip -> addr) provided in hash argument to direct ftrace ops and updates its attachments.
The difference to current unregister_ftrace_direct is
- hash argument that allows to unregister multiple ip -> direct entries at once
- we can call update_ftrace_direct_del multiple times on the same ftrace_ops object, becase we do not need to unregister all entries at once, we can do it gradualy with the help of ftrace_update_ops function
This change will allow us to have simple ftrace_ops for all bpf direct interface users in following changes.
--- include/linux/ftrace.h | 6 +++ kernel/trace/ftrace.c | 112 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 118 insertions(+)
include/linux/ftrace.h +6 -0
@@ -544,6 +544,7 @@ int modify_ftrace_direct(struct ftrace_ops *ops, unsigned long addr);int modify_ftrace_direct_nolock (struct ftrace_ops *ops,unsigned long addr);int update_ftrace_direct_add (struct ftrace_ops *ops,struct ftrace_hash *hash); +int update_ftrace_direct_del (struct ftrace_ops *ops,struct ftrace_hash *hash);void ftrace_stub_direct_tramp (void );
@@ -576,6 +577,11 @@ static inline int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftracereturn -ENODEV ; } +static inline int update_ftrace_direct_del (struct ftrace_ops *ops,struct ftrace_hash *hash) +{ +return -ENODEV ; +} +/* * This must be implemented by the architecture. * It is the way the ftrace direct_ops helper, when called
kernel/trace/ftrace.c +112 -0
118 lines not on this page · raw message
Signature · 1 line
2.52.0
Re: [PATCHv5 bpf-next 5/9] ftrace: Add update_ftrace_direct_del function
Quoted 6 lines · On Mon, 15 Dec 2025 22:13:58 +0100 Jiri Olsa <[email protected]> wrote:
kernel/trace/ftrace.c +6
-0+/** +* hash_sub - substracts @b from @a and returns the result +* @a: struct ftrace_hash object +* @b: struct ftrace_hash object +* +* Returns struct ftrace_hash object on success, NULL on error.
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6395
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+*/ +static struct ftrace_hash *hash_sub (struct ftrace_hash *a,struct ftrace_hash *b) +{ +struct ftrace_func_entry *entry, *del; +struct ftrace_hash *sub; +int size, i; + + sub =alloc_and_copy_ftrace_hash (a->size_bits, a); +if (!sub) + goto error;
Again, this can be just return NULL;
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6398
Quoted 3 lines
kernel/trace/ftrace.c +3
-0+ + size =1 << b->size_bits; +for (i =0 ; i < size; i++) {
You can make this for (int i = 0; ...) too.
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6402
Quoted 4 lines
kernel/trace/ftrace.c +4
-0+hlist_for_each_entry (entry, &b->buckets[i], hlist) { + del =__ftrace_lookup_ip (sub, entry->ip); +if (WARN_ON_ONCE (!del)) + goto error;
And you can remove the error label here too:
if (WARN_ON_ONCE(!del)) {
free_ftrace_hash(sub);
return NULL;
}Quoted 6 lines
kernel/trace/ftrace.c +6
-0+remove_hash_entry (sub, del); +kfree (del); + } + } +return sub; +
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6418
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+ error: +free_ftrace_hash (sub); +return NULL ; +} + +int update_ftrace_direct_del (struct ftrace_ops *ops,struct ftrace_hash *hash) +{ +struct ftrace_hash *old_direct_functions =NULL , *new_direct_functions; +struct ftrace_hash *old_filter_hash, *new_filter_hash =NULL ; +struct ftrace_func_entry *del, *entry;
One variable per line.
Quoted 12 lines
kernel/trace/ftrace.c +12
-0+unsigned long size, i; +int err = -EINVAL ; + +if (!hash_count (hash)) +return -EINVAL ; +if (check_direct_multi (ops)) +return -EINVAL ; +if (!(ops->flags &FTRACE_OPS_FL_ENABLED )) +return -EINVAL ; +if (direct_functions ==EMPTY_HASH ) +return -EINVAL ; +
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6440
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+mutex_lock (&direct_mutex); + + old_filter_hash = ops->func_hash ? ops->func_hash->filter_hash :NULL ; + +if (!hash_count (old_filter_hash)) + goto out_unlock; + +/* Make sure requested entries are already registered. */ + size =1 << hash->size_bits; +for (i =0 ; i < size; i++) {
for (int i = 0; ...)
-- Steve
Quoted 54 lines
kernel/trace/ftrace.c +51
-0+hlist_for_each_entry (entry, &hash->buckets[i], hlist) { + del =__ftrace_lookup_ip (direct_functions, entry->ip); +if (!del || del->direct != entry->direct) + goto out_unlock; + } + } + + err = -ENOMEM ; + new_filter_hash =hash_sub (old_filter_hash, hash); +if (!new_filter_hash) + goto out_unlock; + + new_direct_functions =hash_sub (direct_functions, hash); +if (!new_direct_functions) + goto out_unlock; + +/* If there's nothing left, we need to unregister the ops. */ +if (ftrace_hash_empty (new_filter_hash)) { + err =unregister_ftrace_function (ops); +if (!err) { +/* cleanup for possible another register call */ + ops->func =NULL ; + ops->trampoline =0 ; +ftrace_free_filter (ops); + ops->func_hash->filter_hash =NULL ; + } + }else { + err =ftrace_update_ops (ops, new_filter_hash,EMPTY_HASH ); +/* +* new_filter_hash is dup-ed, so we need to release it anyway, +* old_filter_hash either stays on error or is already released +*/ + } + +if (err) { +/* free the new_direct_functions */ + old_direct_functions = new_direct_functions; + }else { +rcu_assign_pointer (direct_functions, new_direct_functions); + } + + out_unlock: +mutex_unlock (&direct_mutex); + +if (old_direct_functions && old_direct_functions !=EMPTY_HASH ) +call_rcu_tasks (&old_direct_functions->rcu, register_ftrace_direct_cb); +free_ftrace_hash (new_filter_hash); + +return err; +} +#endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */ /**
Re: [PATCHv5 bpf-next 5/9] ftrace: Add update_ftrace_direct_del function
Quoted 12 lines · Steven Rostedt
Quoted 10 lines · On Mon, 15 Dec 2025 22:13:58 +0100 Jiri Olsa <[email protected]> wrote:
kernel/trace/ftrace.c +10
-0+/** +* hash_sub - substracts @b from @a and returns the result +* @a: struct ftrace_hash object +* @b: struct ftrace_hash object +* +* Returns struct ftrace_hash object on success, NULL on error. +*/ +static struct ftrace_hash *hash_sub (struct ftrace_hash *a,struct ftrace_hash *b) +{ +struct ftrace_func_entry *entry, *del;
Quoted 8 lines
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6395
Quoted 6 lines
kernel/trace/ftrace.c +6
-0+struct ftrace_hash *sub; +int size, i; + + sub =alloc_and_copy_ftrace_hash (a->size_bits, a); +if (!sub) + goto error;Again, this can be just return NULL;
ok
Quoted 6 lines
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6398
Quoted 4 lines
kernel/trace/ftrace.c +3
-0+ + size =1 << b->size_bits; +for (i =0 ; i < size; i++) {You can make this for (int i = 0; ...) too.
ok
Quoted 7 lines
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6402
Quoted 5 lines
kernel/trace/ftrace.c +4
-0+hlist_for_each_entry (entry, &b->buckets[i], hlist) { + del =__ftrace_lookup_ip (sub, entry->ip); +if (WARN_ON_ONCE (!del)) + goto error;And you can remove the error label here too:
ok
Quoted 17 lines
if (WARN_ON_ONCE(!del)) { free_ftrace_hash(sub); return NULL; }Quoted 10 lines
kernel/trace/ftrace.c +10
-0+remove_hash_entry (sub, del); +kfree (del); + } + } +return sub; + + error: +free_ftrace_hash (sub); +return NULL ; +}
Quoted 8 lines
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6418
Quoted 6 lines
kernel/trace/ftrace.c +6
-0+ +int update_ftrace_direct_del (struct ftrace_ops *ops,struct ftrace_hash *hash) +{ +struct ftrace_hash *old_direct_functions =NULL , *new_direct_functions; +struct ftrace_hash *old_filter_hash, *new_filter_hash =NULL ; +struct ftrace_func_entry *del, *entry;One variable per line.
ok
Quoted 17 lines
Quoted 17 lines
kernel/trace/ftrace.c +16
-0+unsigned long size, i; +int err = -EINVAL ; + +if (!hash_count (hash)) +return -EINVAL ; +if (check_direct_multi (ops)) +return -EINVAL ; +if (!(ops->flags &FTRACE_OPS_FL_ENABLED )) +return -EINVAL ; +if (direct_functions ==EMPTY_HASH ) +return -EINVAL ; + +mutex_lock (&direct_mutex); + + old_filter_hash = ops->func_hash ? ops->func_hash->filter_hash :NULL ; +
Quoted 8 lines
kernel/trace/ftrace.c int update_ftrace_direct_add(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6440
Quoted 6 lines
kernel/trace/ftrace.c +6
-0+if (!hash_count (old_filter_hash)) + goto out_unlock; + +/* Make sure requested entries are already registered. */ + size =1 << hash->size_bits; +for (i =0 ; i < size; i++) {for (int i = 0; ...)
ack
thanks,
jirka
Jiri Olsa
reviewerPATCH v5 6/9 ftrace: Add update_ftrace_direct_mod function
In reply to Jiri OlsaAdding update_ftrace_direct_mod function that modifies all entries (ip -> direct) provided in hash argument to direct ftrace ops and updates its attachments.
The difference to current modify_ftrace_direct is:
- hash argument that allows to modify multiple ip -> direct entries at once
This change will allow us to have simple ftrace_ops for all bpf direct interface users in following changes.
--- include/linux/ftrace.h | 6 ++++ kernel/trace/ftrace.c | 72 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 78 insertions(+)
include/linux/ftrace.h +6 -0
@@ -545,6 +545,7 @@ int modify_ftrace_direct_nolock(struct ftrace_ops *ops, unsigned long addr);int update_ftrace_direct_add (struct ftrace_ops *ops,struct ftrace_hash *hash);int update_ftrace_direct_del (struct ftrace_ops *ops,struct ftrace_hash *hash); +int update_ftrace_direct_mod (struct ftrace_ops *ops,struct ftrace_hash *hash,bool do_direct_lock);void ftrace_stub_direct_tramp (void );
@@ -582,6 +583,11 @@ static inline int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftracereturn -ENODEV ; } +static inline int update_ftrace_direct_mod (struct ftrace_ops *ops,struct ftrace_hash *hash,bool do_direct_lock) +{ +return -ENODEV ; +} +/* * This must be implemented by the architecture. * It is the way the ftrace direct_ops helper, when called
kernel/trace/ftrace.c +72 -0
78 lines not on this page · raw message
Signature · 1 line
2.52.0
Steven Rostedt
maintainerRe: [PATCHv5 bpf-next 6/9] ftrace: Add update_ftrace_direct_mod function
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6491
Quoted 8 lines · On Mon, 15 Dec 2025 22:13:59 +0100 Jiri Olsa <[email protected]> wrote:
kernel/trace/ftrace.c +0
-0@@ -6489,6 +6489,78 @@ int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash)return err; }
Kerneldoc needed.
Quoted 12 lines
kernel/trace/ftrace.c +12
-0+int update_ftrace_direct_mod (struct ftrace_ops *ops,struct ftrace_hash *hash,bool do_direct_lock) +{ +struct ftrace_func_entry *entry, *tmp; +static struct ftrace_ops tmp_ops = { + .func = ftrace_stub, + .flags =FTRACE_OPS_FL_STUB , + }; +struct ftrace_hash *orig_hash; +unsigned long size, i; +int err = -EINVAL ; + +if (!hash_count (hash))
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6513
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+return -EINVAL ; +if (check_direct_multi (ops)) +return -EINVAL ; +if (!(ops->flags &FTRACE_OPS_FL_ENABLED )) +return -EINVAL ; +if (direct_functions ==EMPTY_HASH ) +return -EINVAL ; + +if (do_direct_lock) +mutex_lock (&direct_mutex);
This optional taking of the direct_mutex lock needs some serious rationale and documentation.
Quoted 17 lines
kernel/trace/ftrace.c +17
-0+ + orig_hash = ops->func_hash ? ops->func_hash->filter_hash :NULL ; +if (!orig_hash) + goto unlock; + +/* Enable the tmp_ops to have the same functions as the direct ops */ +ftrace_ops_init (&tmp_ops); + tmp_ops.func_hash = ops->func_hash; + + err =register_ftrace_function_nolock (&tmp_ops); +if (err) + goto unlock; + +/* +* Call __ftrace_hash_update_ipmodify() here, so that we can call +* ops->ops_func for the ops. This is needed because the above +* register_ftrace_function_nolock() worked on tmp_ops.
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6540
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+*/ + err =__ftrace_hash_update_ipmodify (ops, orig_hash, orig_hash, true); +if (err) + goto out; + +/* +* Now the ftrace_ops_list_func() is called to do the direct callers. +* We can safely change the direct functions attached to each entry. +*/ +mutex_lock (&ftrace_lock);
I'm going to need some time staring at this code. It looks like it may be relying on some internals here.
-- Steve
Quoted 26 lines
kernel/trace/ftrace.c +23
-0+ + size =1 << hash->size_bits; +for (i =0 ; i < size; i++) { +hlist_for_each_entry (entry, &hash->buckets[i], hlist) { + tmp =__ftrace_lookup_ip (direct_functions, entry->ip); +if (!tmp) +continue ; + tmp->direct = entry->direct; + } + } + +mutex_unlock (&ftrace_lock); + +out: +/* Removing the tmp_ops will add the updated direct callers to the functions */ +unregister_ftrace_function (&tmp_ops); + +unlock: +if (do_direct_lock) +mutex_unlock (&direct_mutex); + return err; +} +#endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */ /**
Steven Rostedt
maintainerRe: [PATCHv5 bpf-next 6/9] ftrace: Add update_ftrace_direct_mod function
Quoted 40 lines · On Thu, 18 Dec 2025 10:19:42 -0500 Steven Rostedt <[email protected]> wrote:
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6491
Quoted 8 lines · On Mon, 15 Dec 2025 22:13:59 +0100 Jiri Olsa <[email protected]> wrote:
kernel/trace/ftrace.c +0
-0@@ -6489,6 +6489,78 @@ int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash)return err; }Kerneldoc needed.
Quoted 12 lines
kernel/trace/ftrace.c +12
-0+int update_ftrace_direct_mod (struct ftrace_ops *ops,struct ftrace_hash *hash,bool do_direct_lock) +{ +struct ftrace_func_entry *entry, *tmp; +static struct ftrace_ops tmp_ops = { + .func = ftrace_stub, + .flags =FTRACE_OPS_FL_STUB , + }; +struct ftrace_hash *orig_hash; +unsigned long size, i; +int err = -EINVAL ; + +if (!hash_count (hash))kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6513
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+return -EINVAL ; +if (check_direct_multi (ops)) +return -EINVAL ; +if (!(ops->flags &FTRACE_OPS_FL_ENABLED )) +return -EINVAL ; +if (direct_functions ==EMPTY_HASH ) +return -EINVAL ; + +if (do_direct_lock) +mutex_lock (&direct_mutex);This optional taking of the
direct_mutexlock needs some serious rationale and documentation.
Quoted 6 lines
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6519
Quoted 6 lines
kernel/trace/ftrace.c +6
-0+ + orig_hash = ops->func_hash ? ops->func_hash->filter_hash :NULL ; +if (!orig_hash) + goto unlock; + +/* Enable the tmp_ops to have the same functions as the direct ops */
Add to the comments here:
* In order to modify the direct callers, all the functions need to
* first be calling the ftrace_ops_list_func() and not be connected
* to any direct callers. To do that, create a temporary ops that
* attach to the same functions as the direct ops, and attach that
* first. Then when adding the direct ops, it will use the
* ftrace_ops_list_func(), and this can safely modify what the
* direct ops call.
Or something like that. I want this code to be as clear as day to what it is doing. In a year or two, we will forget, and this will be very confusing to newcomers.
Quoted 25 lines
Quoted 11 lines
kernel/trace/ftrace.c +11
-0+ftrace_ops_init (&tmp_ops); + tmp_ops.func_hash = ops->func_hash; + + err =register_ftrace_function_nolock (&tmp_ops); +if (err) + goto unlock; + +/* +* Call __ftrace_hash_update_ipmodify() here, so that we can call +* ops->ops_func for the ops. This is needed because the above +* register_ftrace_function_nolock() worked on tmp_ops. kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6540
Quoted 10 lines
kernel/trace/ftrace.c +10
-0+*/ + err =__ftrace_hash_update_ipmodify (ops, orig_hash, orig_hash, true); +if (err) + goto out; + +/* +* Now the ftrace_ops_list_func() is called to do the direct callers. +* We can safely change the direct functions attached to each entry. +*/ +mutex_lock (&ftrace_lock);I'm going to need some time staring at this code. It looks like it may be relying on some internals here.
Quoted 4 lines
-- Steve
Quoted 1 line
kernel/trace/ftrace.c +1
-0+
I would add a comment here:
/* Now update the direct functions to point to the new callbacks */
-- Steve
Quoted 25 lines
Quoted 25 lines
kernel/trace/ftrace.c +22
-0+ size =1 << hash->size_bits; +for (i =0 ; i < size; i++) { +hlist_for_each_entry (entry, &hash->buckets[i], hlist) { + tmp =__ftrace_lookup_ip (direct_functions, entry->ip); +if (!tmp) +continue ; + tmp->direct = entry->direct; + } + } + +mutex_unlock (&ftrace_lock); + +out: +/* Removing the tmp_ops will add the updated direct callers to the functions */ +unregister_ftrace_function (&tmp_ops); + +unlock: +if (do_direct_lock) +mutex_unlock (&direct_mutex); + return err; +} +#endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */ /**
Re: [PATCHv5 bpf-next 6/9] ftrace: Add update_ftrace_direct_mod function
In reply to Steven RostedtQuoted 13 lines · Steven Rostedt
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6491
Quoted 8 lines · On Mon, 15 Dec 2025 22:13:59 +0100 Jiri Olsa <[email protected]> wrote:
kernel/trace/ftrace.c +0
-0@@ -6489,6 +6489,78 @@ int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash)return err; }Kerneldoc needed.
will add
Quoted 18 lines
Quoted 18 lines
kernel/trace/ftrace.c +17
-0+int update_ftrace_direct_mod (struct ftrace_ops *ops,struct ftrace_hash *hash,bool do_direct_lock) +{ +struct ftrace_func_entry *entry, *tmp; +static struct ftrace_ops tmp_ops = { + .func = ftrace_stub, + .flags =FTRACE_OPS_FL_STUB , + }; +struct ftrace_hash *orig_hash; +unsigned long size, i; +int err = -EINVAL ; + +if (!hash_count (hash)) +return -EINVAL ; +if (check_direct_multi (ops)) +return -EINVAL ; +if (!(ops->flags &FTRACE_OPS_FL_ENABLED )) +return -EINVAL ;
Quoted 8 lines
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6513
Quoted 5 lines
kernel/trace/ftrace.c +5
-0+if (direct_functions ==EMPTY_HASH ) +return -EINVAL ; + +if (do_direct_lock) +mutex_lock (&direct_mutex);This optional taking of the
direct_mutexlock needs some serious rationale and documentation.
it mirrors the use of modify_ftrace_direct/modify_ftrace_direct_nolock when we do trampoline update from within ftrace_ops->ops_func callback
I'll add comments with more details
Quoted 23 lines
Quoted 23 lines
kernel/trace/ftrace.c +22
-0+ + orig_hash = ops->func_hash ? ops->func_hash->filter_hash :NULL ; +if (!orig_hash) + goto unlock; + +/* Enable the tmp_ops to have the same functions as the direct ops */ +ftrace_ops_init (&tmp_ops); + tmp_ops.func_hash = ops->func_hash; + + err =register_ftrace_function_nolock (&tmp_ops); +if (err) + goto unlock; + +/* +* Call __ftrace_hash_update_ipmodify() here, so that we can call +* ops->ops_func for the ops. This is needed because the above +* register_ftrace_function_nolock() worked on tmp_ops. +*/ + err =__ftrace_hash_update_ipmodify (ops, orig_hash, orig_hash, true); +if (err) + goto out; +
Quoted 8 lines
kernel/trace/ftrace.c int update_ftrace_direct_del(struct ftrace_ops *ops, struct ftrace_hash *hash) · line 6540
Quoted 5 lines
kernel/trace/ftrace.c +5
-0+/* +* Now the ftrace_ops_list_func() is called to do the direct callers. +* We can safely change the direct functions attached to each entry. +*/ +mutex_lock (&ftrace_lock);I'm going to need some time staring at this code. It looks like it may be relying on some internals here.
ok, thanks
jirka
Jiri Olsa
reviewerPATCH v5 7/9 bpf: Add trampoline ip hash table
In reply to Jiri OlsaFollowing changes need to lookup trampoline based on its ip address, adding hash table for that.
--- include/linux/bpf.h | 7 +++++-- kernel/bpf/trampoline.c | 30 +++++++++++++++++++----------- 2 files changed, 24 insertions(+), 13 deletions(-)
include/linux/bpf.h +5 -2
@@ -1307,14 +1307,17 @@ struct bpf_tramp_image { };struct bpf_trampoline { -/* hlist for trampoline_table */ -struct hlist_node hlist; +/* hlist for trampoline_key_table */ +struct hlist_node hlist_key; +/* hlist for trampoline_ip_table */ +struct hlist_node hlist_ip;struct ftrace_ops *fops;/* serializes access to fields of this trampoline */ struct mutex mutex;refcount_t refcnt;u32 flags;u64 key; +unsigned long ip;struct {struct btf_func_model model;void *addr;
kernel/bpf/trampoline.c +19 -11
@@ -24,9 +24,10 @@ const struct bpf_prog_ops bpf_extension_prog_ops = {#define TRAMPOLINE_HASH_BITS 10#define TRAMPOLINE_TABLE_SIZE (1 << TRAMPOLINE_HASH_BITS) -static struct hlist_head trampoline_table[TRAMPOLINE_TABLE_SIZE ]; +static struct hlist_head trampoline_key_table[TRAMPOLINE_TABLE_SIZE ]; +static struct hlist_head trampoline_ip_table[TRAMPOLINE_TABLE_SIZE ]; -/* serializes access to trampoline_table */ +/* serializes access to trampoline tables */ static DEFINE_MUTEX (trampoline_mutex);#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
@@ -135,15 +136,15 @@ void bpf_image_ksym_del(struct bpf_ksym *ksym) PAGE_SIZE, true, ksym->name); } -static struct bpf_trampoline *bpf_trampoline_lookup (u64 key) +static struct bpf_trampoline *bpf_trampoline_lookup (u64 key,unsigned long ip) {struct bpf_trampoline *tr;struct hlist_head *head;int i;mutex_lock (&trampoline_mutex); - head = &trampoline_table[hash_64 (key,TRAMPOLINE_HASH_BITS )]; -hlist_for_each_entry (tr, head, hlist) { + head = &trampoline_key_table[hash_64 (key,TRAMPOLINE_HASH_BITS )]; +hlist_for_each_entry (tr, head, hlist_key) {if (tr->key == key) {refcount_inc (&tr->refcnt); goto out;
@@ -164,8 +165,12 @@ static struct bpf_trampoline *bpf_trampoline_lookup(u64 key)#endif tr->key = key; -INIT_HLIST_NODE (&tr->hlist); -hlist_add_head (&tr->hlist, head); + tr->ip =ftrace_location (ip); +INIT_HLIST_NODE (&tr->hlist_key); +INIT_HLIST_NODE (&tr->hlist_ip); +hlist_add_head (&tr->hlist_key, head); + head = &trampoline_ip_table[hash_64 (tr->ip,TRAMPOLINE_HASH_BITS )]; +hlist_add_head (&tr->hlist_ip, head);refcount_set (&tr->refcnt,1 );mutex_init (&tr->mutex);for (i =0 ; i <BPF_TRAMP_MAX ; i++)
@@ -846,7 +851,7 @@ void bpf_trampoline_unlink_cgroup_shim(struct bpf_prog *prog) prog->aux->attach_btf_id);bpf_lsm_find_cgroup_shim (prog, &bpf_func); - tr =bpf_trampoline_lookup (key); + tr =bpf_trampoline_lookup (key,0 );if (WARN_ON_ONCE (!tr))return ;
@@ -866,7 +871,7 @@ struct bpf_trampoline *bpf_trampoline_get(u64 key, {struct bpf_trampoline *tr; - tr =bpf_trampoline_lookup (key); + tr =bpf_trampoline_lookup (key, tgt_info->tgt_addr);if (!tr)return NULL ;
@@ -902,7 +907,8 @@ void bpf_trampoline_put(struct bpf_trampoline *tr)* fexit progs. The fentry-only trampoline will be freed via * multiple rcu callbacks. */ -hlist_del (&tr->hlist); +hlist_del (&tr->hlist_key); +hlist_del (&tr->hlist_ip);if (tr->fops) {ftrace_free_filter (tr->fops);kfree (tr->fops);
@@ -1175,7 +1181,9 @@ static int __init init_trampolines(void)int i;for (i =0 ; i <TRAMPOLINE_TABLE_SIZE ; i++) -INIT_HLIST_HEAD (&trampoline_table[i]); +INIT_HLIST_HEAD (&trampoline_key_table[i]); +for (i =0 ; i <TRAMPOLINE_TABLE_SIZE ; i++) +INIT_HLIST_HEAD (&trampoline_ip_table[i]);return 0 ; }late_initcall (init_trampolines);
Signature · 1 line
2.52.0
Jiri Olsa
reviewerPATCH v5 8/9 ftrace: Factor ftrace_ops ops_func interface
In reply to Jiri OlsaWe are going to remove "ftrace_ops->private == bpf_trampoline" setup in following changes.
Adding ip argument to ftrace_ops_func_t callback function, so we can use it to look up the trampoline.
--- include/linux/ftrace.h | 2 +- kernel/bpf/trampoline.c | 3 ++- kernel/trace/ftrace.c | 6 +++--- 3 files changed, 6 insertions(+), 5 deletions(-)
include/linux/ftrace.h +1 -1
@@ -403,7 +403,7 @@ enum ftrace_ops_cmd {* Negative on failure. The return value is dependent on the * callback. */ -typedef int (*ftrace_ops_func_t )(struct ftrace_ops *op,enum ftrace_ops_cmd cmd); +typedef int (*ftrace_ops_func_t )(struct ftrace_ops *op,unsigned long ip,enum ftrace_ops_cmd cmd);#ifdef CONFIG_DYNAMIC_FTRACE
kernel/bpf/trampoline.c +2 -1
@@ -33,7 +33,8 @@ static DEFINE_MUTEX(trampoline_mutex);#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS static int bpf_trampoline_update (struct bpf_trampoline *tr,bool lock_direct_mutex); -static int bpf_tramp_ftrace_ops_func (struct ftrace_ops *ops,enum ftrace_ops_cmd cmd) +static int bpf_tramp_ftrace_ops_func (struct ftrace_ops *ops,unsigned long ip, +enum ftrace_ops_cmd cmd) {struct bpf_trampoline *tr = ops->private;int ret =0 ;
kernel/trace/ftrace.c +3 -3
@@ -2049,7 +2049,7 @@ static int __ftrace_hash_update_ipmodify(struct ftrace_ops *ops,*/ if (!ops->ops_func)return -EBUSY ; - ret = ops->ops_func (ops,FTRACE_OPS_CMD_ENABLE_SHARE_IPMODIFY_SELF ); + ret = ops->ops_func (ops, rec->ip,FTRACE_OPS_CMD_ENABLE_SHARE_IPMODIFY_SELF );if (ret)return ret; }else if (is_ipmodify) {
@@ -8983,7 +8983,7 @@ static int prepare_direct_functions_for_ipmodify(struct ftrace_ops *ops)if (!op->ops_func)return -EBUSY ; - ret = op->ops_func (op,FTRACE_OPS_CMD_ENABLE_SHARE_IPMODIFY_PEER ); + ret = op->ops_func (op, ip,FTRACE_OPS_CMD_ENABLE_SHARE_IPMODIFY_PEER );if (ret)return ret; }
@@ -9030,7 +9030,7 @@ static void cleanup_direct_functions_after_ipmodify(struct ftrace_ops *ops)/* The cleanup is optional, ignore any errors */ if (found_op && op->ops_func) - op->ops_func (op,FTRACE_OPS_CMD_DISABLE_SHARE_IPMODIFY_PEER ); + op->ops_func (op, ip,FTRACE_OPS_CMD_DISABLE_SHARE_IPMODIFY_PEER ); } }mutex_unlock (&direct_mutex);
Signature · 1 line
2.52.0
Re: [PATCHv5 bpf-next 8/9] ftrace: Factor ftrace_ops ops_func interface
Quoted 7 lines · On Mon, 15 Dec 2025 22:14:01 +0100 Jiri Olsa <[email protected]> wrote:
We are going to remove "
ftrace_ops->private==bpf_trampoline" setup in following changes.Adding ip argument to
ftrace_ops_func_tcallback function, so we can use it to look up the trampoline.Signed-off-by Jiri Olsa <[email protected]>
This mostly touches bpf code so:
-- Steve
Jiri Olsa
reviewerPATCH v5 9/9 bpf,x86: Use single ftrace_ops for direct calls
In reply to Jiri OlsaUsing single ftrace_ops for direct calls update instead of allocating ftrace_ops object for each trampoline.
With single ftrace_ops object we can use update_ftrace_direct_* api that allows multiple ip sites updates on single ftrace_ops object.
Adding HAVE_SINGLE_FTRACE_DIRECT_OPS config option to be enabled on each arch that supports this.
At the moment we can enable this only on x86 arch, because arm relies on ftrace_ops object representing just single trampoline image (stored in ftrace_ops::direct_call). Ach that do not support this will continue to use *_ftrace_direct api.
--- arch/x86/Kconfig | 1 + kernel/bpf/trampoline.c | 195 ++++++++++++++++++++++++++++++++++------ kernel/trace/Kconfig | 3 + kernel/trace/ftrace.c | 7 +- 4 files changed, 177 insertions(+), 29 deletions(-)
arch/x86/Kconfig +1 -0
@@ -335,6 +335,7 @@ config X86 select SCHED_SMT if SMP select ARCH_SUPPORTS_SCHED_CLUSTER if SMP select ARCH_SUPPORTS_SCHED_MC if SMP + select HAVE_SINGLE_FTRACE_DIRECT_OPS if X86_64 && DYNAMIC_FTRACE_WITH_DIRECT_CALLS config INSTRUCTION_DECODER def_bool y
kernel/bpf/trampoline.c +167 -28
246 lines not on this page · raw message
kernel/trace/Kconfig +3 -0
@@ -50,6 +50,9 @@ config HAVE_DYNAMIC_FTRACE_WITH_REGS config HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS bool +config HAVE_SINGLE_FTRACE_DIRECT_OPS + bool + config HAVE_DYNAMIC_FTRACE_WITH_CALL_OPS bool
kernel/trace/ftrace.c +6 -1
@@ -2605,8 +2605,13 @@ unsigned long ftrace_find_rec_direct(unsigned long ip)static void call_direct_funcs (unsigned long ip,unsigned long pip,struct ftrace_ops *ops,struct ftrace_regs *fregs) { -unsigned long addr =READ_ONCE (ops->direct_call); +unsigned long addr; +#ifdef CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS + addr =ftrace_find_rec_direct (ip); +#else + addr =READ_ONCE (ops->direct_call); +#endif if (!addr)return ;
Signature · 1 line
2.52.0
Steven Rostedt
maintainerRe: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls
Quoted 6 lines · On Mon, 15 Dec 2025 22:14:02 +0100 Jiri Olsa <[email protected]> wrote:
Using single
ftrace_opsfor direct calls update instead of allocatingftrace_opsobject for each trampoline.With single
ftrace_opsobject we can use update_ftrace_direct_* api that allows multiple ip sites updates on singleftrace_opsobject.
Quoted 6 lines
Adding
HAVE_SINGLE_FTRACE_DIRECT_OPSconfig option to be enabled on each arch that supports this.At the moment we can enable this only on x86 arch, because arm relies on
ftrace_opsobject representing just single trampoline image (stored inftrace_ops::direct_call). Ach that do not support this will continue
My back "Ach" and doesn't support me well. ;-)
Quoted 15 lines
to use
*_ftrace_directapi.Signed-off-by Jiri Olsa <[email protected]>--- arch/x86/Kconfig | 1 + kernel/bpf/trampoline.c | 195 ++++++++++++++++++++++++++++++++++------ kernel/trace/Kconfig | 3 + kernel/trace/ftrace.c | 7 +- 4 files changed, 177 insertions(+), 29 deletions(-)arch/x86/Kconfig +0
-0
arch/x86/Kconfig config X86 · line 338
Quoted 4 lines
arch/x86/Kconfig +1
-0@@ -335,6 +335,7 @@ config X86 select SCHED_SMT if SMP select ARCH_SUPPORTS_SCHED_CLUSTER if SMP select ARCH_SUPPORTS_SCHED_MC if SMP + select HAVE_SINGLE_FTRACE_DIRECT_OPS if X86_64 && DYNAMIC_FTRACE_WITH_DIRECT_CALLS
You can remove the "&& DYNAMIC_FTRACE_WITH_DIRECT_CALLS" part by having the config depend on it (see below).
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 36
Quoted 12 lines
arch/x86/Kconfig +0
-0config INSTRUCTION_DECODER def_bool ykernel/bpf/trampoline.c +1
-0@@ -33,12 +33,40 @@ static DEFINE_MUTEX(trampoline_mutex);#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS static int bpf_trampoline_update (struct bpf_trampoline *tr,bool lock_direct_mutex); +#ifdef CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS
Make this:
#ifdef CONFIG_SINGLE_FTRACE_DIRECT_OPS
for the suggested modification in the Kconfig below.
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 42
Quoted 6 lines
kernel/bpf/trampoline.c +6
-0+static struct bpf_trampoline *direct_ops_ip_lookup (struct ftrace_ops *ops,unsigned long ip) +{ +struct hlist_head *head_ip; +struct bpf_trampoline *tr; + +mutex_lock (&trampoline_mutex);
guard(mutex)(&trampoline_mutex);
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 45
Quoted 3 lines
kernel/bpf/trampoline.c +3
-0+ head_ip = &trampoline_ip_table[hash_64 (ip,TRAMPOLINE_HASH_BITS )]; +hlist_for_each_entry (tr, head_ip, hlist_ip) { +if (tr->ip == ip)
return NULL;
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 50
Quoted 7 lines
kernel/bpf/trampoline.c +5
-0+ goto out; + } + tr =NULL ; +out: +mutex_unlock (&trampoline_mutex);
No need for the above
Quoted 24 lines
kernel/bpf/trampoline.c +14
-1+ return tr; +} +#else +static struct bpf_trampoline *direct_ops_ip_lookup (struct ftrace_ops *ops,unsigned long ip) +{ +return ops->private; +} +#endif /* CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS */ +static int bpf_tramp_ftrace_ops_func (struct ftrace_ops *ops,unsigned long ip,enum ftrace_ops_cmd cmd) { -struct bpf_trampoline *tr = ops->private; +struct bpf_trampoline *tr;int ret =0 ; + tr =direct_ops_ip_lookup (ops, ip); +if (!tr) +return -EINVAL ; +if (cmd ==FTRACE_OPS_CMD_ENABLE_SHARE_IPMODIFY_SELF ) {kernel/bpf/trampoline.c +0
-0/* This is called inside register_ftrace_direct_multi(), so * tr->mutex is already locked.
kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 169
Quoted 5 lines
kernel/bpf/trampoline.c +2
-0@@ -137,6 +165,139 @@ void bpf_image_ksym_del(struct bpf_ksym *ksym) PAGE_SIZE, true, ksym->name); } +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS +#ifdef CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS
Replace the above two with:
#ifdef CONFIG_SINGLE_FTRACE_DIRECT_OPS
Quoted 38 lines
kernel/bpf/trampoline.c +38
-0+/* +* We have only single direct_ops which contains all the direct call +* sites and is the only global ftrace_ops for all trampolines. +* +* We use 'update_ftrace_direct_*' api for attachment. +*/ +struct ftrace_ops direct_ops = { + .ops_func = bpf_tramp_ftrace_ops_func, +}; + +static int direct_ops_alloc (struct bpf_trampoline *tr) +{ + tr->fops = &direct_ops; +return 0 ; +} + +static void direct_ops_free (struct bpf_trampoline *tr) { } + +static struct ftrace_hash *hash_from_ip (struct bpf_trampoline *tr,void *ptr) +{ +unsigned long ip, addr = (unsigned long ) ptr; +struct ftrace_hash *hash; + + ip =ftrace_location (tr->ip); +if (!ip) +return NULL ; + hash =alloc_ftrace_hash (FTRACE_HASH_DEFAULT_BITS ); +if (!hash) +return NULL ; +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (!add_hash_entry_direct (hash, ip, addr)) { +free_ftrace_hash (hash); +return NULL ; + } +return hash; +} +
kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 217
Quoted 10 lines
kernel/bpf/trampoline.c +10
-0+static int direct_ops_add (struct bpf_trampoline *tr,void *addr) +{ +struct ftrace_hash *hash =hash_from_ip (tr, addr); +int err = -ENOMEM ; + +if (hash) + err =update_ftrace_direct_add (tr->fops, hash); +free_ftrace_hash (hash); +return err; +}
I think these functions would be cleaner as:
{
struct ftrace_hash *hash = hash_from_ip(tr, addr);
int err;
if (!hash)
return -ENOMEM;
err = update_ftrace_direct_*(tr->fops, hash);
free_ftrace_hash(hash);
return err;
}Quoted 36 lines
kernel/bpf/trampoline.c +36
-0+ +static int direct_ops_del (struct bpf_trampoline *tr,void *addr) +{ +struct ftrace_hash *hash =hash_from_ip (tr, addr); +int err = -ENOMEM ; + +if (hash) + err =update_ftrace_direct_del (tr->fops, hash); +free_ftrace_hash (hash); +return err; +} + +static int direct_ops_mod (struct bpf_trampoline *tr,void *addr,bool lock_direct_mutex) +{ +struct ftrace_hash *hash =hash_from_ip (tr, addr); +int err = -ENOMEM ; + +if (hash) + err =update_ftrace_direct_mod (tr->fops, hash, lock_direct_mutex); +free_ftrace_hash (hash); +return err; +} +#else +/* +* We allocate ftrace_ops object for each trampoline and it contains +* call site specific for that trampoline. +* +* We use *_ftrace_direct api for attachment. +*/ +static int direct_ops_alloc (struct bpf_trampoline *tr) +{ + tr->fops =kzalloc (sizeof (struct ftrace_ops ),GFP_KERNEL ); +if (!tr->fops) +return -ENOMEM ; + tr->fops->private = tr; + tr->fops->ops_func = bpf_tramp_ftrace_ops_func;
kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 263
Quoted 10 lines
kernel/bpf/trampoline.c +10
-0+return 0 ; +} + +static void direct_ops_free (struct bpf_trampoline *tr) +{ +if (tr->fops) { +ftrace_free_filter (tr->fops); +kfree (tr->fops); + } +}
Why not:
static void direct_ops_free(struct bpf_trampoline *tr)
{
if (!tr->fops)
return;
ftrace_free_filter(tr->fops);
kfree(tr->fops);
}?
Quoted 25 lines
kernel/bpf/trampoline.c +25
-0+ +static int direct_ops_add (struct bpf_trampoline *tr,void *ptr) +{ +unsigned long addr = (unsigned long ) ptr; +struct ftrace_ops *ops = tr->fops; +int ret; + +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); + + ret =ftrace_set_filter_ip (ops, tr->ip,0 ,1 ); +if (ret) +return ret; +return register_ftrace_direct (ops, addr); +} + +static int direct_ops_del (struct bpf_trampoline *tr,void *addr) +{ +return unregister_ftrace_direct (tr->fops, (long )addr, false); +} + +static int direct_ops_mod (struct bpf_trampoline *tr,void *ptr,bool lock_direct_mutex) +{ +unsigned long addr = (unsigned long ) ptr; +struct ftrace_ops *ops = tr->fops;
kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 298
Quoted 10 lines
kernel/bpf/trampoline.c +10
-0+ +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (lock_direct_mutex) +return modify_ftrace_direct (ops, addr); + return modify_ftrace_direct_nolock(ops, addr); +} +#endif /* CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS */ +#else +static void direct_ops_free (struct bpf_trampoline *tr) { }
This is somewhat inconsistent with direct_ops_alloc() that has:
#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
if (direct_ops_alloc(tr)) {
kfree(tr);
tr = NULL;
goto out;
}#endif
Now, if you wrap the direct_ops_free() too, we can remove the
#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
part with my kconfig suggestion. Otherwise keep the kconfig as is, but I would add a stub function for direct_ops_alloc() too.
Quoted 22 lines
kernel/bpf/trampoline.c +3
-4+#endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */ +static struct bpf_trampoline *bpf_trampoline_lookup (u64 key,unsigned long ip) {struct bpf_trampoline *tr;@@ -155,14 +316,11 @@ static struct bpf_trampoline *bpf_trampoline_lookup(u64 key, unsigned long ip)if (!tr) goto out;#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS - tr->fops =kzalloc (sizeof (struct ftrace_ops ),GFP_KERNEL ); -if (!tr->fops) { +if (direct_ops_alloc (tr)) {kfree (tr); tr =NULL ; goto out; } - tr->fops->private = tr; - tr->fops->ops_func = bpf_tramp_ftrace_ops_func;#endif tr->key = key;
kernel/bpf/trampoline.c static int unregister_fentry(struct bpf_trampoline *tr, u32 orig_flags, · line 367
Quoted 5 lines
kernel/bpf/trampoline.c +1
-1@@ -206,7 +364,7 @@ static int unregister_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;if (tr->func.ftrace_managed) - ret =unregister_ftrace_direct (tr->fops, (long )old_addr, false); + ret =direct_ops_del (tr, old_addr);
Doesn't this need a wrapper too?
Quoted 7 lines
kernel/bpf/trampoline.c +0
-0else ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr,NULL );@@ -220,15 +378,7 @@ static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;if (tr->func.ftrace_managed) {
kernel/bpf/trampoline.c static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags, · line 381
Quoted 10 lines
kernel/bpf/trampoline.c +1
-9-unsigned long addr = (unsigned long ) new_addr; - -if (bpf_trampoline_use_jmp (tr->flags)) - addr =ftrace_jmp_set (addr); - -if (lock_direct_mutex) - ret =modify_ftrace_direct (tr->fops, addr); -else - ret =modify_ftrace_direct_nolock (tr->fops, addr); + ret =direct_ops_mod (tr, new_addr, lock_direct_mutex);
and this.
Quoted 7 lines
kernel/bpf/trampoline.c +0
-0}else { ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr, new_addr);@@ -251,15 +401,7 @@ static int register_fentry(struct bpf_trampoline *tr, void *new_addr) }if (tr->func.ftrace_managed) {
kernel/bpf/trampoline.c static int register_fentry(struct bpf_trampoline *tr, void *new_addr) · line 404
Quoted 10 lines
kernel/bpf/trampoline.c +1
-9-unsigned long addr = (unsigned long ) new_addr; - -if (bpf_trampoline_use_jmp (tr->flags)) - addr =ftrace_jmp_set (addr); - - ret =ftrace_set_filter_ip (tr->fops, (unsigned long )ip,0 ,1 ); -if (ret) -return ret; - ret =register_ftrace_direct (tr->fops, addr); + ret =direct_ops_add (tr, new_addr);
Ditto.
Quoted 20 lines
kernel/bpf/trampoline.c +1
-4}else { ret =bpf_trampoline_update_fentry (tr,0 ,NULL , new_addr); }@@ -910,10 +1052,7 @@ void bpf_trampoline_put(struct bpf_trampoline *tr)*/ hlist_del (&tr->hlist_key);hlist_del (&tr->hlist_ip); -if (tr->fops) { -ftrace_free_filter (tr->fops); -kfree (tr->fops); - } +direct_ops_free (tr);kfree (tr); out:mutex_unlock (&trampoline_mutex);kernel/trace/Kconfig +0
-0
kernel/trace/Kconfig config HAVE_DYNAMIC_FTRACE_WITH_REGS · line 55
Quoted 6 lines
kernel/trace/Kconfig +3
-0@@ -50,6 +50,9 @@ config HAVE_DYNAMIC_FTRACE_WITH_REGS config HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS bool +config HAVE_SINGLE_FTRACE_DIRECT_OPS + bool +
Now you could add:
config SINGLE_FTRACE_DIRECT_OPS
bool default y depends on HAVE_SINGLE_FTRACE_DIRECT_OPS && DYNAMIC_FTRACE_WITH_DIRECT_CALLS
-- Steve
Quoted 22 lines
kernel/trace/Kconfig +0
-0config HAVE_DYNAMIC_FTRACE_WITH_CALL_OPS boolkernel/trace/ftrace.c +6
-1@@ -2605,8 +2605,13 @@ unsigned long ftrace_find_rec_direct(unsigned long ip)static void call_direct_funcs (unsigned long ip,unsigned long pip,struct ftrace_ops *ops,struct ftrace_regs *fregs) { -unsigned long addr =READ_ONCE (ops->direct_call); +unsigned long addr; +#ifdef CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS + addr =ftrace_find_rec_direct (ip); +#else + addr =READ_ONCE (ops->direct_call); +#endif if (!addr)return ;
Re: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls
Quoted 9 lines · Steven Rostedt
Quoted 6 lines · On Mon, 15 Dec 2025 22:14:02 +0100 Jiri Olsa <[email protected]> wrote:
Using single
ftrace_opsfor direct calls update instead of allocatingftrace_opsobject for each trampoline.With single
ftrace_opsobject we can use update_ftrace_direct_* api that allows multiple ip sites updates on singleftrace_opsobject.
Quoted 8 lines
Quoted 6 lines
Adding
HAVE_SINGLE_FTRACE_DIRECT_OPSconfig option to be enabled on each arch that supports this.At the moment we can enable this only on x86 arch, because arm relies on
ftrace_opsobject representing just single trampoline image (stored inftrace_ops::direct_call). Ach that do not support this will continueMy back "Ach" and doesn't support me well. ;-)
heh, should have been 'Archs' ;-)
Quoted 23 lines
Quoted 16 lines
to use
*_ftrace_directapi.Signed-off-by Jiri Olsa <[email protected]>--- arch/x86/Kconfig | 1 + kernel/bpf/trampoline.c | 195 ++++++++++++++++++++++++++++++++++------ kernel/trace/Kconfig | 3 + kernel/trace/ftrace.c | 7 +- 4 files changed, 177 insertions(+), 29 deletions(-)arch/x86/Kconfig +0
-0arch/x86/Kconfig config X86 · line 338
Quoted 4 lines
arch/x86/Kconfig +1
-0@@ -335,6 +335,7 @@ config X86 select SCHED_SMT if SMP select ARCH_SUPPORTS_SCHED_CLUSTER if SMP select ARCH_SUPPORTS_SCHED_MC if SMP + select HAVE_SINGLE_FTRACE_DIRECT_OPS if X86_64 && DYNAMIC_FTRACE_WITH_DIRECT_CALLSYou can remove the "&&
DYNAMIC_FTRACE_WITH_DIRECT_CALLS" part by having the config depend on it (see below).
...
Quoted 20 lines
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 36
Quoted 13 lines
config
INSTRUCTION_DECODERarch/x86/Kconfig +0
-0def_bool ykernel/bpf/trampoline.c +1
-0@@ -33,12 +33,40 @@ static DEFINE_MUTEX(trampoline_mutex);#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS static int bpf_trampoline_update (struct bpf_trampoline *tr,bool lock_direct_mutex); +#ifdef CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS Make this:
#ifdef
CONFIG_SINGLE_FTRACE_DIRECT_OPSfor the suggested modification in the
Kconfigbelow.
Quoted 8 lines
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 42
Quoted 6 lines
kernel/bpf/trampoline.c +6
-0+static struct bpf_trampoline *direct_ops_ip_lookup (struct ftrace_ops *ops,unsigned long ip) +{ +struct hlist_head *head_ip; +struct bpf_trampoline *tr; + +mutex_lock (&trampoline_mutex);guard(mutex)(&trampoline_mutex);
right, will change
Quoted 11 lines
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 45
Quoted 4 lines
kernel/bpf/trampoline.c +3
-0+ head_ip = &trampoline_ip_table[hash_64 (ip,TRAMPOLINE_HASH_BITS )]; +hlist_for_each_entry (tr, head_ip, hlist_ip) { +if (tr->ip == ip)return NULL;Quoted 2 lines
kernel/bpf/trampoline.c +2
-0+ goto out; + }
Quoted 5 lines
kernel/bpf/trampoline.c static DEFINE_MUTEX(trampoline_mutex); · line 50
Quoted 3 lines
kernel/bpf/trampoline.c +3
-0+ tr =NULL ; +out: +mutex_unlock (&trampoline_mutex);No need for the above
yep
Quoted 34 lines
Quoted 25 lines
kernel/bpf/trampoline.c +14
-1+ return tr; +} +#else +static struct bpf_trampoline *direct_ops_ip_lookup (struct ftrace_ops *ops,unsigned long ip) +{ +return ops->private; +} +#endif /* CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS */ +static int bpf_tramp_ftrace_ops_func (struct ftrace_ops *ops,unsigned long ip,enum ftrace_ops_cmd cmd) { -struct bpf_trampoline *tr = ops->private; +struct bpf_trampoline *tr;int ret =0 ; + tr =direct_ops_ip_lookup (ops, ip); +if (!tr) +return -EINVAL ; +if (cmd ==FTRACE_OPS_CMD_ENABLE_SHARE_IPMODIFY_SELF ) {/* This is called inside register_ftrace_direct_multi(), so * tr->mutex is already locked. kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 169
Quoted 5 lines
kernel/bpf/trampoline.c +2
-0@@ -137,6 +165,139 @@ void bpf_image_ksym_del(struct bpf_ksym *ksym) PAGE_SIZE, true, ksym->name); } +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS +#ifdef CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS Replace the above two with:
#ifdef
CONFIG_SINGLE_FTRACE_DIRECT_OPS
...
Quoted 52 lines
Quoted 39 lines
kernel/bpf/trampoline.c +38
-0+/* +* We have only single direct_ops which contains all the direct call +* sites and is the only global ftrace_ops for all trampolines. +* +* We use 'update_ftrace_direct_*' api for attachment. +*/ +struct ftrace_ops direct_ops = { + .ops_func = bpf_tramp_ftrace_ops_func, +}; + +static int direct_ops_alloc (struct bpf_trampoline *tr) +{ + tr->fops = &direct_ops; +return 0 ; +} + +static void direct_ops_free (struct bpf_trampoline *tr) { } + +static struct ftrace_hash *hash_from_ip (struct bpf_trampoline *tr,void *ptr) +{ +unsigned long ip, addr = (unsigned long ) ptr; +struct ftrace_hash *hash; + + ip =ftrace_location (tr->ip); +if (!ip) +return NULL ; + hash =alloc_ftrace_hash (FTRACE_HASH_DEFAULT_BITS ); +if (!hash) +return NULL ; +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (!add_hash_entry_direct (hash, ip, addr)) { +free_ftrace_hash (hash); +return NULL ; + } +return hash; +} +kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 217
Quoted 10 lines
kernel/bpf/trampoline.c +10
-0+static int direct_ops_add (struct bpf_trampoline *tr,void *addr) +{ +struct ftrace_hash *hash =hash_from_ip (tr, addr); +int err = -ENOMEM ; + +if (hash) + err =update_ftrace_direct_add (tr->fops, hash); +free_ftrace_hash (hash); +return err; +}I think these functions would be cleaner as:
Quoted 11 lines
{
struct ftrace_hash *hash = hash_from_ip(tr, addr);
int err;
if (!hash)
return -ENOMEM;
err = update_ftrace_direct_*(tr->fops, hash);
free_ftrace_hash(hash);
return err;
}np, will change
Quoted 51 lines
Quoted 38 lines
kernel/bpf/trampoline.c +36
-0+ +static int direct_ops_del (struct bpf_trampoline *tr,void *addr) +{ +struct ftrace_hash *hash =hash_from_ip (tr, addr); +int err = -ENOMEM ; + +if (hash) + err =update_ftrace_direct_del (tr->fops, hash); +free_ftrace_hash (hash); +return err; +} + +static int direct_ops_mod (struct bpf_trampoline *tr,void *addr,bool lock_direct_mutex) +{ +struct ftrace_hash *hash =hash_from_ip (tr, addr); +int err = -ENOMEM ; + +if (hash) + err =update_ftrace_direct_mod (tr->fops, hash, lock_direct_mutex); +free_ftrace_hash (hash); +return err; +} +#else +/* +* We allocate ftrace_ops object for each trampoline and it contains +* call site specific for that trampoline. +* +* We use *_ftrace_direct api for attachment. +*/ +static int direct_ops_alloc (struct bpf_trampoline *tr) +{ + tr->fops =kzalloc (sizeof (struct ftrace_ops ),GFP_KERNEL ); +if (!tr->fops) +return -ENOMEM ; + tr->fops->private = tr; + tr->fops->ops_func = bpf_tramp_ftrace_ops_func;kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 263
Quoted 10 lines
kernel/bpf/trampoline.c +10
-0+return 0 ; +} + +static void direct_ops_free (struct bpf_trampoline *tr) +{ +if (tr->fops) { +ftrace_free_filter (tr->fops); +kfree (tr->fops); + } +}Why not:
Quoted 8 lines
static void
direct_ops_free(struct bpf_trampoline *tr){ if (!tr->fops) return; ftrace_free_filter(tr->fops); kfree(tr->fops); }
same pattern like above, ok
Quoted 47 lines
?
Quoted 25 lines
kernel/bpf/trampoline.c +25
-0+ +static int direct_ops_add (struct bpf_trampoline *tr,void *ptr) +{ +unsigned long addr = (unsigned long ) ptr; +struct ftrace_ops *ops = tr->fops; +int ret; + +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); + + ret =ftrace_set_filter_ip (ops, tr->ip,0 ,1 ); +if (ret) +return ret; +return register_ftrace_direct (ops, addr); +} + +static int direct_ops_del (struct bpf_trampoline *tr,void *addr) +{ +return unregister_ftrace_direct (tr->fops, (long )addr, false); +} + +static int direct_ops_mod (struct bpf_trampoline *tr,void *ptr,bool lock_direct_mutex) +{ +unsigned long addr = (unsigned long ) ptr; +struct ftrace_ops *ops = tr->fops;kernel/bpf/trampoline.c void bpf_image_ksym_del(struct bpf_ksym *ksym) · line 298
Quoted 10 lines
kernel/bpf/trampoline.c +10
-0+ +if (bpf_trampoline_use_jmp (tr->flags)) + addr =ftrace_jmp_set (addr); +if (lock_direct_mutex) +return modify_ftrace_direct (ops, addr); + return modify_ftrace_direct_nolock(ops, addr); +} +#endif /* CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS */ +#else +static void direct_ops_free (struct bpf_trampoline *tr) { }This is somewhat inconsistent with
direct_ops_alloc()that has:#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS if (direct_ops_alloc(tr)) { kfree(tr); tr = NULL; goto out; }
Quoted 6 lines
#endif
Now, if you wrap the
direct_ops_free()too, we can remove the
#ifdefCONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
part with my kconfig suggestion. Otherwise keep the kconfig as is, but I would add a stub function fordirect_ops_alloc()too.
ah right.. I think let's do the kconfig change you suggest to make this simpler
Quoted 25 lines
Quoted 25 lines
kernel/bpf/trampoline.c +3
-4+#endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */ +static struct bpf_trampoline *bpf_trampoline_lookup (u64 key,unsigned long ip) {struct bpf_trampoline *tr;@@ -155,14 +316,11 @@ static struct bpf_trampoline *bpf_trampoline_lookup(u64 key, unsigned long ip)if (!tr) goto out;#ifdef CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS - tr->fops =kzalloc (sizeof (struct ftrace_ops ),GFP_KERNEL ); -if (!tr->fops) { +if (direct_ops_alloc (tr)) {kfree (tr); tr =NULL ; goto out; } - tr->fops->private = tr; - tr->fops->ops_func = bpf_tramp_ftrace_ops_func;#endif tr->key = key;@@ -206,7 +364,7 @@ static int unregister_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;
Quoted 5 lines
kernel/bpf/trampoline.c static int unregister_fentry(struct bpf_trampoline *tr, u32 orig_flags, · line 367
Quoted 3 lines
kernel/bpf/trampoline.c +1
-1if (tr->func.ftrace_managed) - ret =unregister_ftrace_direct (tr->fops, (long )old_addr, false); + ret =direct_ops_del (tr, old_addr);Doesn't this need a wrapper too?
yep
Quoted 27 lines
Quoted 8 lines
kernel/bpf/trampoline.c +0
-0else ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr,NULL );@@ -220,15 +378,7 @@ static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,int ret;if (tr->func.ftrace_managed) {kernel/bpf/trampoline.c static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags, · line 381
Quoted 10 lines
kernel/bpf/trampoline.c +1
-9-unsigned long addr = (unsigned long ) new_addr; - -if (bpf_trampoline_use_jmp (tr->flags)) - addr =ftrace_jmp_set (addr); - -if (lock_direct_mutex) - ret =modify_ftrace_direct (tr->fops, addr); -else - ret =modify_ftrace_direct_nolock (tr->fops, addr); + ret =direct_ops_mod (tr, new_addr, lock_direct_mutex);and this.
Quoted 6 lines
kernel/bpf/trampoline.c +0
-0}else { ret =bpf_trampoline_update_fentry (tr, orig_flags, old_addr, new_addr);@@ -251,15 +401,7 @@ static int register_fentry(struct bpf_trampoline *tr, void *new_addr) }
Quoted 13 lines
kernel/bpf/trampoline.c static int register_fentry(struct bpf_trampoline *tr, void *new_addr) · line 404
Quoted 11 lines
kernel/bpf/trampoline.c +1
-9if (tr->func.ftrace_managed) { -unsigned long addr = (unsigned long ) new_addr; - -if (bpf_trampoline_use_jmp (tr->flags)) - addr =ftrace_jmp_set (addr); - - ret =ftrace_set_filter_ip (tr->fops, (unsigned long )ip,0 ,1 ); -if (ret) -return ret; - ret =register_ftrace_direct (tr->fops, addr); + ret =direct_ops_add (tr, new_addr);Ditto.
yes
Quoted 30 lines
Quoted 21 lines
kernel/bpf/trampoline.c +1
-4}else { ret =bpf_trampoline_update_fentry (tr,0 ,NULL , new_addr); }@@ -910,10 +1052,7 @@ void bpf_trampoline_put(struct bpf_trampoline *tr)*/ hlist_del (&tr->hlist_key);hlist_del (&tr->hlist_ip); -if (tr->fops) { -ftrace_free_filter (tr->fops); -kfree (tr->fops); - } +direct_ops_free (tr);kfree (tr); out:mutex_unlock (&trampoline_mutex);kernel/trace/Kconfig +0
-0kernel/trace/Kconfig config HAVE_DYNAMIC_FTRACE_WITH_REGS · line 55
Quoted 6 lines
kernel/trace/Kconfig +3
-0@@ -50,6 +50,9 @@ config HAVE_DYNAMIC_FTRACE_WITH_REGS config HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS bool +config HAVE_SINGLE_FTRACE_DIRECT_OPS + bool +Now you could add:
Quoted 4 lines
config
SINGLE_FTRACE_DIRECT_OPSbool default y depends on HAVE_SINGLE_FTRACE_DIRECT_OPS && DYNAMIC_FTRACE_WITH_DIRECT_CALLS
ok, the dependency is more ovbvious, will change
thanks,
jirka
Re: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls
Quoted 19 lines · Jiri Olsa
Quoted 14 lines
kernel/trace/Kconfig config HAVE_DYNAMIC_FTRACE_WITH_REGS · line 55
Quoted 11 lines
kernel/trace/Kconfig +3
-0@@ -50,6 +50,9 @@ config HAVE_DYNAMIC_FTRACE_WITH_REGS config HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS bool +config HAVE_SINGLE_FTRACE_DIRECT_OPS + bool +Now you could add:
Quoted 4 lines
config
SINGLE_FTRACE_DIRECT_OPSbool default y depends on HAVE_SINGLE_FTRACE_DIRECT_OPS && DYNAMIC_FTRACE_WITH_DIRECT_CALLS
Quoted 4 lines
ok, the dependency is more ovbvious, will change
thanks,
jirka
actualy, it seems that having it the original way with adding the rest of the wrappers for !CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS case is easier AFAICS
jirka
---
arch/x86/Kconfig +1 -0
@@ -336,6 +336,7 @@ config X86 select SCHED_SMT if SMP select ARCH_SUPPORTS_SCHED_CLUSTER if SMP select ARCH_SUPPORTS_SCHED_MC if SMP + select HAVE_SINGLE_FTRACE_DIRECT_OPS if X86_64 && DYNAMIC_FTRACE_WITH_DIRECT_CALLS config INSTRUCTION_DECODER def_bool y
kernel/bpf/trampoline.c +187 -30
268 lines not on this page · raw message
kernel/trace/Kconfig +3 -0
@@ -50,6 +50,9 @@ config HAVE_DYNAMIC_FTRACE_WITH_REGS config HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS bool +config HAVE_SINGLE_FTRACE_DIRECT_OPS + bool + config HAVE_DYNAMIC_FTRACE_WITH_CALL_OPS bool
kernel/trace/ftrace.c +6 -1
@@ -2631,8 +2631,13 @@ unsigned long ftrace_find_rec_direct(unsigned long ip)static void call_direct_funcs (unsigned long ip,unsigned long pip,struct ftrace_ops *ops,struct ftrace_regs *fregs) { -unsigned long addr =READ_ONCE (ops->direct_call); +unsigned long addr; +#ifdef CONFIG_HAVE_SINGLE_FTRACE_DIRECT_OPS + addr =ftrace_find_rec_direct (ip); +#else + addr =READ_ONCE (ops->direct_call); +#endif if (!addr)return ;
Steven Rostedt
maintainerRe: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls
Quoted 3 lines · On Sun, 28 Dec 2025 16:22:18 +0100 Jiri Olsa <[email protected]> wrote:
actualy, it seems that having it the original way with adding the rest of the wrappers for !CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS case is easier AFAICS
I'm fine either way.
-- Steve
kernel test robot
build botRe: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls
In reply to Jiri Olsakernel test robot noticed the following build errors:
Hi Jiri,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Jiri-Olsa/ftrace-bpf-Remove-FTRACE_OPS_FL_JMP-ftrace_ops-flag/20251216-052916 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master patch link: https://lore.kernel.org/r/20251215211402.353056-10-jolsa%40kernel.org patch subject: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20251221/[email protected]/config) compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project b324c9f4fa112d61a553bf489b5f4f7ceea05ea8) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251221/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
>> kernel/bpf/trampoline.c:367:9: error: call to undeclared function 'direct_ops_del'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
367 | ret = direct_ops_del(tr, old_addr);
| ^
kernel/bpf/trampoline.c:367:9: note: did you mean 'direct_ops_free'?
kernel/bpf/trampoline.c:298:13: note: 'direct_ops_free' declared here
298 | static void direct_ops_free(struct bpf_trampoline *tr) { }
| ^
>> kernel/bpf/trampoline.c:381:9: error: call to undeclared function 'direct_ops_mod'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
381 | ret = direct_ops_mod(tr, new_addr, lock_direct_mutex);
| ^
kernel/bpf/trampoline.c:381:9: note: did you mean 'direct_ops_free'?
kernel/bpf/trampoline.c:298:13: note: 'direct_ops_free' declared here
298 | static void direct_ops_free(struct bpf_trampoline *tr) { }
| ^
>> kernel/bpf/trampoline.c:404:9: error: call to undeclared function 'direct_ops_add'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
404 | ret = direct_ops_add(tr, new_addr);
| ^
kernel/bpf/trampoline.c:404:9: note: did you mean 'direct_ops_free'?
kernel/bpf/trampoline.c:298:13: note: 'direct_ops_free' declared here
298 | static void direct_ops_free(struct bpf_trampoline *tr) { }
| ^3 errors generated.
vim +/direct_ops_del +367 kernel/bpf/trampoline.c
360
361 static int unregister_fentry(struct bpf_trampoline *tr, u32 orig_flags,
362 void *old_addr)
363 {
364 int ret;
365
366 if (tr->func.ftrace_managed)
> 367 ret = direct_ops_del(tr, old_addr);
368 else
369 ret = bpf_trampoline_update_fentry(tr, orig_flags, old_addr, NULL);
370
371 return ret;
372 }
373
374 static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,
375 void *old_addr, void *new_addr,
376 bool lock_direct_mutex)
377 {
378 int ret;
379
380 if (tr->func.ftrace_managed) {
> 381 ret = direct_ops_mod(tr, new_addr, lock_direct_mutex);
382 } else {
383 ret = bpf_trampoline_update_fentry(tr, orig_flags, old_addr,
384 new_addr);
385 }
386 return ret;
387 }
388
389 /* first time registering */
390 static int register_fentry(struct bpf_trampoline *tr, void *new_addr)
391 {
392 void *ip = tr->func.addr;
393 unsigned long faddr;
394 int ret;
395
396 faddr = ftrace_location((unsigned long)ip);
397 if (faddr) {
398 if (!tr->fops)
399 return -ENOTSUPP;
400 tr->func.ftrace_managed = true;
401 }
402
403 if (tr->func.ftrace_managed) {
> 404 ret = direct_ops_add(tr, new_addr); 405 } else {
406 ret = bpf_trampoline_update_fentry(tr, 0, NULL, new_addr);
407 }
408
409 return ret;
410 }
411
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
kernel test robot
build botRe: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls
In reply to Jiri Olsakernel test robot noticed the following build errors:
Hi Jiri,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Jiri-Olsa/ftrace-bpf-Remove-FTRACE_OPS_FL_JMP-ftrace_ops-flag/20251216-052916 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master patch link: https://lore.kernel.org/r/20251215211402.353056-10-jolsa%40kernel.org patch subject: [PATCHv5 bpf-next 9/9] bpf,x86: Use single ftrace_ops for direct calls config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20251221/[email protected]/config) compiler: arc-linux-gcc (GCC) 15.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251221/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
kernel/bpf/trampoline.c: In function 'unregister_fentry':
>> kernel/bpf/trampoline.c:367:23: error: implicit declaration of function 'direct_ops_del'; did you mean 'direct_ops_free'? [-Wimplicit-function-declaration]
367 | ret = direct_ops_del(tr, old_addr);
| ^~~~~~~~~~~~~~
| direct_ops_free
kernel/bpf/trampoline.c: In function 'modify_fentry':
>> kernel/bpf/trampoline.c:381:23: error: implicit declaration of function 'direct_ops_mod'; did you mean 'direct_ops_free'? [-Wimplicit-function-declaration]
381 | ret = direct_ops_mod(tr, new_addr, lock_direct_mutex);
| ^~~~~~~~~~~~~~
| direct_ops_free
kernel/bpf/trampoline.c: In function 'register_fentry':
>> kernel/bpf/trampoline.c:404:23: error: implicit declaration of function 'direct_ops_add'; did you mean 'direct_ops_free'? [-Wimplicit-function-declaration]
404 | ret = direct_ops_add(tr, new_addr);
| ^~~~~~~~~~~~~~
| direct_ops_freevim +367 kernel/bpf/trampoline.c
360
361 static int unregister_fentry(struct bpf_trampoline *tr, u32 orig_flags,
362 void *old_addr)
363 {
364 int ret;
365
366 if (tr->func.ftrace_managed)
> 367 ret = direct_ops_del(tr, old_addr);
368 else
369 ret = bpf_trampoline_update_fentry(tr, orig_flags, old_addr, NULL);
370
371 return ret;
372 }
373
374 static int modify_fentry(struct bpf_trampoline *tr, u32 orig_flags,
375 void *old_addr, void *new_addr,
376 bool lock_direct_mutex)
377 {
378 int ret;
379
380 if (tr->func.ftrace_managed) {
> 381 ret = direct_ops_mod(tr, new_addr, lock_direct_mutex);
382 } else {
383 ret = bpf_trampoline_update_fentry(tr, orig_flags, old_addr,
384 new_addr);
385 }
386 return ret;
387 }
388
389 /* first time registering */
390 static int register_fentry(struct bpf_trampoline *tr, void *new_addr)
391 {
392 void *ip = tr->func.addr;
393 unsigned long faddr;
394 int ret;
395
396 faddr = ftrace_location((unsigned long)ip);
397 if (faddr) {
398 if (!tr->fops)
399 return -ENOTSUPP;
400 tr->func.ftrace_managed = true;
401 }
402
403 if (tr->func.ftrace_managed) {
> 404 ret = direct_ops_add(tr, new_addr); 405 } else {
406 ret = bpf_trampoline_update_fentry(tr, 0, NULL, new_addr);
407 }
408
409 return ret;
410 }
411
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki