You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BPF_PROG_TYPE_RAW_TRACEPOINTs can be executed nested on the same CPU, as
they do not increment bpf_prog_active while executing.
This enables three levels of nesting, to support
- a kprobe or raw tp or perf event,
- another one of the above that irq context happens to call, and
- another one in nmi context
(at most one of which may be a kprobe or perf event).
Fixes: 20b9d7a ("bpf: avoid excessive stack usage for perf_sample_data")
Signed-off-by: Matt Mullins <[email protected]>
Acked-by: Andrii Nakryiko <[email protected]>
Acked-by: Daniel Borkmann <[email protected]>
Signed-off-by: Alexei Starovoitov <[email protected]>
(cherry picked from commit 9594dc3)
Orabug: 31865809
Signed-off-by: Alan Maguire <[email protected]>
Reviewed-by: Liam Merwick <[email protected]>
Conflicts:
kernel/trace/bpf_trace.c
Conflicts are contextual plus the patch addresses nesting for raw
tracepoints; raw tracepoint support is not in UEK5 so this portion
of the patch isn't relevant.
Signed-off-by: Somasundaram Krishnasamy <[email protected]>
0 commit comments