allow cpumask kfuncs in tracepoint, kprobe, perf event
Subsystems (3)
v2 cover allow cpumask kfuncs in tracepoint, kprobe, perf event
It is possible to call a cpumask kfunc within a raw tp_btf program but not possible within tracepoint, kprobe, or perf event programs. Currently, the verifier receives -EACCESS from fetch_kfunc_meta() as a result of not finding any kfunc hook associated with these program types.
This patch series adds new kfunc hooks and maps them to program types where needed. The additional registration of the three program types mentioned is done for the cpumask kfuncs allowing them to be called within these types of programs.
Pre-submission CI run: https://github.com/kernel-patches/bpf/pull/7600
v2:
- create new kfunc hooks for tracepoint and perf event
- map tracepoint, and perf event prog types to kfunc hooks
- register cpumask kfuncs with prog types in focus
- expand existing verifier tests for cpumask kfuncs
v1:
- map tracepoint type progs to tracing kfunc hook
- new selftests for calling cpumask kfuncs in tracepoint prog
---
JP Kobryn (3):
bpf: new btf kfunc hooks for tracepoint and perf event
bpf: register additional prog types with cpumask kfuncs bpf/selftests: coverage for new program types using cpumask kfuncs
kernel/bpf/btf.c | 6 +++++ kernel/bpf/cpumask.c | 3 +++ .../bpf/progs/verifier_kfunc_prog_types.c | 24 +++++++++++++++++++ 3 files changed, 33 insertions(+)
Signature · 1 line
2.46.0
PATCH v2 1/3 bpf: new btf kfunc hooks for tracepoint and perf event
The additional hooks (and prog-to-hook mapping) for tracepoint and perf event programs allow for registering kfuncs to be used within these program types.
--- kernel/bpf/btf.c | 6 ++++++ 1 file changed, 6 insertions(+)
kernel/bpf/btf.c +6 -0
@@ -210,6 +210,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_TC ,BTF_KFUNC_HOOK_STRUCT_OPS ,BTF_KFUNC_HOOK_TRACING , +BTF_KFUNC_HOOK_TRACEPOINT ,BTF_KFUNC_HOOK_SYSCALL ,BTF_KFUNC_HOOK_FMODRET , BTF_KFUNC_HOOK_CGROUP_SKB,
@@ -219,6 +220,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_LWT ,BTF_KFUNC_HOOK_NETFILTER ,BTF_KFUNC_HOOK_KPROBE , +BTF_KFUNC_HOOK_PERF_EVENT , BTF_KFUNC_HOOK_MAX, };
@@ -8306,6 +8308,8 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)case BPF_PROG_TYPE_TRACING :case BPF_PROG_TYPE_LSM :return BTF_KFUNC_HOOK_TRACING ; +case BPF_PROG_TYPE_TRACEPOINT : +return BTF_KFUNC_HOOK_TRACEPOINT ;case BPF_PROG_TYPE_SYSCALL :return BTF_KFUNC_HOOK_SYSCALL ;case BPF_PROG_TYPE_CGROUP_SKB :
@@ -8326,6 +8330,8 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)return BTF_KFUNC_HOOK_NETFILTER ;case BPF_PROG_TYPE_KPROBE :return BTF_KFUNC_HOOK_KPROBE ; +case BPF_PROG_TYPE_PERF_EVENT : +return BTF_KFUNC_HOOK_PERF_EVENT ;default :return BTF_KFUNC_HOOK_MAX ; }
Signature · 1 line
2.46.0
Re: [PATCH bpf-next v2 1/3] bpf: new btf kfunc hooks for tracepoint and perf event
Quoted 31 lines · JP Kobryn
The additional hooks (and prog-to-hook mapping) for tracepoint and perf event programs allow for registering kfuncs to be used within these program types.
Signed-off-by JP Kobryn <[email protected]>--- kernel/bpf/btf.c | 6 ++++++ 1 file changed, 6 insertions(+)kernel/bpf/btf.c +2
-0@@ -210,6 +210,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_TC ,BTF_KFUNC_HOOK_STRUCT_OPS ,BTF_KFUNC_HOOK_TRACING , +BTF_KFUNC_HOOK_TRACEPOINT ,BTF_KFUNC_HOOK_SYSCALL ,BTF_KFUNC_HOOK_FMODRET , BTF_KFUNC_HOOK_CGROUP_SKB,@@ -219,6 +220,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_LWT ,BTF_KFUNC_HOOK_NETFILTER ,BTF_KFUNC_HOOK_KPROBE , +BTF_KFUNC_HOOK_PERF_EVENT , BTF_KFUNC_HOOK_MAX, };
kernel/bpf/btf.c static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type) · line 8312
Quoted 5 lines
kernel/bpf/btf.c +2
-0@@ -8306,6 +8308,8 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)case BPF_PROG_TYPE_TRACING :case BPF_PROG_TYPE_LSM :return BTF_KFUNC_HOOK_TRACING ; +case BPF_PROG_TYPE_TRACEPOINT : +return BTF_KFUNC_HOOK_TRACEPOINT ;
why special case tp and perf_event and only limit them to cpumask? The following would be equally safe, no?
case BPF_PROG_TYPE_TRACING:
case BPF_PROG_TYPE_LSM:
+ case BPF_PROG_TYPE_TRACEPOINT:
+ case BPF_PROG_TYPE_PERF_EVENT:
return BTF_KFUNC_HOOK_TRACING;
?
Re: [PATCH bpf-next v2 1/3] bpf: new btf kfunc hooks for tracepoint and perf event
Quoted 32 lines · Alexei Starovoitov
Quoted 30 lines · JP Kobryn
The additional hooks (and prog-to-hook mapping) for tracepoint and perf event programs allow for registering kfuncs to be used within these program types.
Signed-off-by JP Kobryn <[email protected]>--- kernel/bpf/btf.c | 6 ++++++ 1 file changed, 6 insertions(+)kernel/bpf/btf.c +2
-0@@ -210,6 +210,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_TC ,BTF_KFUNC_HOOK_STRUCT_OPS ,BTF_KFUNC_HOOK_TRACING , +BTF_KFUNC_HOOK_TRACEPOINT ,BTF_KFUNC_HOOK_SYSCALL ,BTF_KFUNC_HOOK_FMODRET , BTF_KFUNC_HOOK_CGROUP_SKB,@@ -219,6 +220,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_LWT ,BTF_KFUNC_HOOK_NETFILTER ,BTF_KFUNC_HOOK_KPROBE , +BTF_KFUNC_HOOK_PERF_EVENT , BTF_KFUNC_HOOK_MAX, };
Quoted 9 lines
kernel/bpf/btf.c static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type) · line 8312
Quoted 6 lines
kernel/bpf/btf.c +2
-0@@ -8306,6 +8308,8 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)case BPF_PROG_TYPE_TRACING :case BPF_PROG_TYPE_LSM :return BTF_KFUNC_HOOK_TRACING ; +case BPF_PROG_TYPE_TRACEPOINT : +return BTF_KFUNC_HOOK_TRACEPOINT ;why special case tp and
perf_eventand only limit them to cpumask? The following would be equally safe, no?
Assuming we don't have kfuncs that accepts program context (like bpf_get_stack(), if it was a kfunc) and that doesn't access bpf_run_ctx (like bpf_get_func_ip()). We just need to be careful about adding new special kfuncs like that going forward (not sure how to best ensure we don't forget, though). Other than that I agree that it's all "tracing".
Quoted 6 lines
case
BPF_PROG_TYPE_TRACING:
caseBPF_PROG_TYPE_LSM:
+ caseBPF_PROG_TYPE_TRACEPOINT:
+ caseBPF_PROG_TYPE_PERF_EVENT:return BTF_KFUNC_HOOK_TRACING;?
Re: [PATCH bpf-next v2 1/3] bpf: new btf kfunc hooks for tracepoint and perf event
Quoted 44 lines · Andrii Nakryiko
Quoted 32 lines · Alexei Starovoitov
Quoted 30 lines · JP Kobryn
The additional hooks (and prog-to-hook mapping) for tracepoint and perf event programs allow for registering kfuncs to be used within these program types.
Signed-off-by JP Kobryn <[email protected]>--- kernel/bpf/btf.c | 6 ++++++ 1 file changed, 6 insertions(+)kernel/bpf/btf.c +2
-0@@ -210,6 +210,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_TC ,BTF_KFUNC_HOOK_STRUCT_OPS ,BTF_KFUNC_HOOK_TRACING , +BTF_KFUNC_HOOK_TRACEPOINT ,BTF_KFUNC_HOOK_SYSCALL ,BTF_KFUNC_HOOK_FMODRET , BTF_KFUNC_HOOK_CGROUP_SKB,@@ -219,6 +220,7 @@ enum btf_kfunc_hook {BTF_KFUNC_HOOK_LWT ,BTF_KFUNC_HOOK_NETFILTER ,BTF_KFUNC_HOOK_KPROBE , +BTF_KFUNC_HOOK_PERF_EVENT , BTF_KFUNC_HOOK_MAX, };Quoted 9 lines
kernel/bpf/btf.c static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type) · line 8312
Quoted 6 lines
kernel/bpf/btf.c +2
-0@@ -8306,6 +8308,8 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)case BPF_PROG_TYPE_TRACING :case BPF_PROG_TYPE_LSM :return BTF_KFUNC_HOOK_TRACING ; +case BPF_PROG_TYPE_TRACEPOINT : +return BTF_KFUNC_HOOK_TRACEPOINT ;why special case tp and
perf_eventand only limit them to cpumask? The following would be equally safe, no?
Quoted 6 lines
Assuming we don't have kfuncs that accepts program context (like
bpf_get_stack(), if it was a kfunc) and that doesn't accessbpf_run_ctx(likebpf_get_func_ip()). We just need to be careful about adding new special kfuncs like that going forward (not sure how to best ensure we don't forget, though). Other than that I agree that it's all "tracing".
What Alexei is suggesting works. I did something similar in v1[0] where I associated BPF_PROG_TYPE_TRACEPOINT with BTF_KFUNC_HOOK_TRACING. But it occurred to me that this circumvents the registration process during initialization, so I want to make sure if this is or is not acceptable. See below for my thoughts.
Quoted 7 lines
Quoted 7 lines
case
BPF_PROG_TYPE_TRACING:
caseBPF_PROG_TYPE_LSM:
+ caseBPF_PROG_TYPE_TRACEPOINT:
+ caseBPF_PROG_TYPE_PERF_EVENT:return BTF_KFUNC_HOOK_TRACING;?
With this change, anywhere we do register_btf_kfunc_id_set(BPF_PROG_TYPE_TRACING, &some_kfunc_set), BTF_KFUNC_HOOK_TRACING becomes allowed. So even if we never register the extra program types like PROG_TYPE_PERF_EVENT, we still allow them as a side effect since at runtime the program type mapping returns HOOK_TRACING. Any program type associated with this hook will be allowed even though not explicitly registered. My take on v2 was moving towards the element of least surprise, and thought the explicit registration with the new hooks made sense. I'm fine though, if we prefer this style above with the implicit registration. Let me know and I can make a v3 if needed.
Re: [PATCH bpf-next v2 1/3] bpf: new btf kfunc hooks for tracepoint and perf event
Quoted 8 lines · JP Kobryn
With this change, anywhere we do
register_btf_kfunc_id_set(BPF_PROG_TYPE_TRACING, &some_kfunc_set),BTF_KFUNC_HOOK_TRACINGbecomes allowed. So even if we never register the extra program types likePROG_TYPE_PERF_EVENT, we still allow them as a side effect since at runtime the program type mapping returnsHOOK_TRACING. Any program type associated with this hook will be allowed even though not explicitly registered.
Correct. kfuncs differentiate by type of their arguments. prog_type -> helper was an old style when context was the only thing we had. So we had to differentiate by prog_type. kfuncs are currently register by prog_type too, but that will go away. We're planning to do large refactoring in that area to satisfy sched-ext requests. It's not the prog type that would allow or disallow certain kfuncs but rather hook point plus custom flags.
PATCH v2 2/3 bpf: register additional prog types with cpumask kfuncs
In reply to JP KobrynAllow the cpumask family of kfuncs to be called within tracepoint, kprobe, and perf event programs.
--- kernel/bpf/cpumask.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/bpf/cpumask.c +3 -0
@@ -475,6 +475,9 @@ static int __init cpumask_kfunc_init(void) ret = ret ?:register_btf_kfunc_id_set (BPF_PROG_TYPE_TRACING , &cpumask_kfunc_set); ret = ret ?:register_btf_kfunc_id_set (BPF_PROG_TYPE_STRUCT_OPS , &cpumask_kfunc_set); ret = ret ?:register_btf_kfunc_id_set (BPF_PROG_TYPE_SYSCALL , &cpumask_kfunc_set); + ret = ret ?:register_btf_kfunc_id_set (BPF_PROG_TYPE_TRACEPOINT , &cpumask_kfunc_set); + ret = ret ?:register_btf_kfunc_id_set (BPF_PROG_TYPE_KPROBE , &cpumask_kfunc_set); + ret = ret ?:register_btf_kfunc_id_set (BPF_PROG_TYPE_PERF_EVENT , &cpumask_kfunc_set);return ret ?:register_btf_id_dtor_kfuncs (cpumask_dtors,ARRAY_SIZE (cpumask_dtors),THIS_MODULE );
Signature · 1 line
2.46.0
PATCH v2 3/3 bpf/selftests: coverage for new program types using cpumask kfuncs
In reply to JP KobrynThis coverage ensures that the cpumask family of kfuncs are allowed within tracepoint, kprobe, and perf event programs.
--- .../bpf/progs/verifier_kfunc_prog_types.c | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+)
tools/testing/selftests/bpf/progs/verifier_kfunc_prog_types.c +24 -0
@@ -120,3 +120,27 @@ int BPF_PROG(cpumask_kfunc_syscall)cpumask_kfunc_load_test ();return 0 ; } + +SEC("tracepoint") +__success +int BPF_PROG (cpumask_kfunc_tracepoint ) +{ +cpumask_kfunc_load_test (); +return 0 ; +} + +SEC("kprobe") +__success +int BPF_PROG (cpumask_kfunc_kprobe ) +{ +cpumask_kfunc_load_test (); +return 0 ; +} + +SEC("perf_event") +__success +int BPF_PROG (cpumask_kfunc_perf_event ) +{ +cpumask_kfunc_load_test (); +return 0 ; +}
Signature · 1 line
2.46.0