1.2.1: Bug fix release:
Single bug fix (#1) that fixes regression in `perf` tool caused by libbpf
resetting its custom catch-all `SEC()` handler on explicit
`bpf_program__set_type()` call.
Given setting custom `SEC()` handlers is rarely used and pretty
esoteric feature of libbpf, most users should not be affected.
1.2.2: One more fix:
- Fix (#2) possible double-free in USDT-related libbpf code, which
happens when libbpf runs out of space in `__bpf_usdt_specs` map due
to having too many unique USDT specs. Running out of space can be
mitigated by bumping up `BPF_USDT_MAX_SPEC_CNT` define before including
`bpf/usdt.bpf.h` header in BPF-side code.
This will prevent the double-free as a side effect (and will make it
possible to successfully attach all requested USDTs), which is a
recommended work-around for libbpf versions prior to v1.2.2.
Link: e4d3827e5d#1
Link: f117080307#2
libbpf 1.x breaks too many packages to do a hard transition: just keep
both packages for a while longer.
See https://github.com/libbpf/libbpf/issues/590 for discussion with upstream
This installs the linux/btf.h header in libbpf, which is necessarily
compatible with bpf/btf.h
Note that we also ship the linux header's linux/btf.h with glibc,
but explicit buildInputs should have priority over default headers so
hopefully this one will always be used.
continuation of #109595
pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.
python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
