Vincent Bernat <ber...@debian.org> writes:
> ❦ 4 novembre 2019 18:55 +0530, Vasudeva Sathish Kamath
> <vasu...@debian.org>:
Copying Ritesh who is also the maintainer of the libbpfcc
>
> I get the same results. Also, it doesn't work with a 5.2 kernel either.
> Using "strace -febpf", I see the following:
>
> bpf(BPF_MAP_CREATE, {map_type=BPF_MAP_TYPE_PERCPU_HASH,
> key_size=2296983664, value_size=8, max_entries=8, map_flags=0x1000 /*
> BPF_F_??? */, inner_map_fd=0, map_name="", map_ifindex=0}, 112) = -1
> EINVAL (Invalid argument)
>
> So, the values seem bogus. libbpfcc has been updated recently and it
> doesn't seem to manage a stable ABI. Just recompiling bpftrace against
> the new one makes it work. I am tempted to just bump the version and
> call it a day.
I can confirm this, I rebuilt the bpftrace and it started working. I
faced similar issue with bpfcc-tools where it was segfaulting on some
function in libbpfcc but then when I built and installed upstream
library it suddenly started working. I think this is similar case.
You can rebuild with a Debian version bump and close this bug.
On a side note: I'm just wondering since all these tools are closely
related (bpfcc-tools, libbpfcc, bpftrace) can we have a team and
co-maintain them. Asking because till libbpfcc stabilizes whenever a
new version of libbpfcc is to be released we can make sure we will
rebuild the bpftrace and any other dependencies which uses libbpfcc.
I'll be happy to join the team for maintaining these tools.
Cheers,
I
