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
What reproduces the bug? Provide code if possible.
The latest version (v0.20.1) of bpftrace run against a 4.19 kernel (specifying the path to the BTF file through the BPFTRACE_BTF environment variable) fails to load (apparently any) program. v0.19.1 works fine in the same environment. I managed to bisect the issue as being caused by #2804.
System
OS: Linux 4.19.306 #1 SMP Thu Feb 1 17:01:42 UTC 2024
Arch: x86_64
Build
version: v0.20.1
LLVM: 17.0.6
unsafe probe: no
bfd: no
libdw (DWARF support): yes
Kernel helpers
probe_read: yes
probe_read_str: yes
probe_read_user: no
probe_read_user_str: no
probe_read_kernel: no
probe_read_kernel_str: no
get_current_cgroup_id: yes
send_signal: no
override_return: yes
get_boot_ns: no
dpath: no
skboutput: no
get_tai_ns: no
get_func_ip: no
jiffies64: no
Kernel features
Instruction limit: 131072
Loop support: no
btf: yes
module btf: no
map batch: no
uprobe refcount (depends on Build:bcc bpf_attach_uprobe refcount): no
Map types
hash: yes
percpu hash: yes
array: yes
percpu array: yes
stack_trace: yes
perf_event_array: yes
ringbuf: no
Probe types
kprobe: yes
tracepoint: yes
perf_event: yes
kfunc: no
kprobe_multi: no
uprobe_multi: no
raw_tp_special: no
iter: no
The text was updated successfully, but these errors were encountered:
Kind 13 is BTF_KIND_FUNC_PROTO which was added by torvalds/linux@2667a2626f4d to kernel version 5.0. To support a kernel as old as 4.19, we'd probably have to add an option not to emit BTF for our programs. That will prevent some features to be used but should make at least basic probes work.
FWIW, I'm not sure how this will work once we start delegating more things (like prog loading) to libbpf. It's supposed to be backwards-compatible but I'm not sure to what extent.
What reproduces the bug? Provide code if possible.
The latest version (v0.20.1) of bpftrace run against a 4.19 kernel (specifying the path to the BTF file through the
BPFTRACE_BTF
environment variable) fails to load (apparently any) program. v0.19.1 works fine in the same environment. I managed to bisect the issue as being caused by #2804.I'm running a 4.19 VM through https://github.com/cilium/little-vm-helper:
bpftrace --info
outputThe text was updated successfully, but these errors were encountered: