Debian Patches
Status for bpfcc/0.35.0+ds-1.1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| fix-install-path.patch | fix-install-path Minor issue. Patch can be submitted upstream |
Ritesh Raj Sarraf <rrs@debian.org> | no | 2020-07-17 | ||
| 2001_fix_path_to_deadloc.c.patch | Fix the path to deadlock.c used in deadlock-bpfcc Move the deadlock.c from /usr/sbin/ to /usr/share/bpfcc-tools/ and update the python script to use it from this path |
Vasudev Kamath <vasudev@debian.org> | not-needed | 2020-09-04 | ||
| 2002_fix_netqtop.c_path.patch | Fix the path of netqtop.c on Debian systems On Debian system we install the netqtop.c to /usr/share/bpfcc-tools folder adjust the path in utility to match this. |
Vasudev Kamath <vasudev@debian.org> | not-needed | 2020-11-06 | ||
| 2003-libbpf-tools-debian.patch | Compile libbpf-tools with system installed libbpf | Vasudev Kamath <vasudev@debian.org> | not-needed | |||
| 0001-Cleanup-existing-temporary-kernel-headers-path.patch | [PATCH] Cleanup existing temporary kernel headers path If kernel headers are not installed in the usual place, the BPF tools try to look them up in /tmp/kheaders-$(uname -r)/, even when this directory is owned by another user. This can be exploited for denial of service, or likely something worse. To reproduce, run this as a normal user: $ mkdir /tmp/kheaders-$(uname -r)/ $ mkdir -p /tmp/kheaders-$(uname -r)/include/linux/ $ echo "#error this header is malicious" > /tmp/kheaders-$(uname -r)/include/linux/kconfig.h Then run this as root: # opensnoop-bpfcc In file included from <built-in>:1: ././include/linux/kconfig.h:1:2: error: this header is malicious #error this header is malicious ^ In file included from <built-in>:2: /virtual/include/bcc/bpf.h:12:10: fatal error: 'linux/types.h' file not found #include <linux/types.h> ^~~~~~~~~~~~~~~ 2 errors generated. Traceback (most recent call last): File "/usr/sbin/opensnoop-bpfcc", line 261, in <module> b = BPF(text='') ^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/bcc/__init__.py", line 476, in __init__ raise Exception("Failed to compile BPF module %s" % (src_file or "<text>")) Exception: Failed to compile BPF module <text> |
Ritesh Raj Sarraf <rrs@debian.org> | no | 2023-01-23 | ||
| 0002-clang-21.patch | commit 8c5c96ad3beeed2fa827017f451a952306826974 Fix a build failure with clang21 (#5369) The build error message: src/cc/frontends/clang/loader.cc:400:73: error: no matching function for call to ‘clang::TextDiagnosticPrinter::TextDiagnosticPrinter( llvm::raw_fd_ostream&, clang::DiagnosticOptions*)’ 400 | auto diag_client = new TextDiagnosticPrinter(llvm::errs(), &*diag_opts); | ^ The llvm commit https://github.com/llvm/llvm-project/pull/139584 caused the build failure. Adjust the code properly and the error is fixed. diff --git a/src/cc/frontends/clang/loader.cc b/src/cc/frontends/clang/loader.cc index 07dc9d6a..6f8387aa 100644 |
yonghong-song <ys114321@gmail.com> | not-needed | debian | https://github.com/iovisor/bcc/commit/8c5c96ad3beeed2fa827017f451a952306826974 | 2025-12-20 |
All known versions for source package 'bpfcc'
- 0.35.0+ds-2~exp1 (experimental)
- 0.35.0+ds-1.1 (sid)
- 0.35.0+ds-1 (forky)
- 0.31.0+ds-7 (trixie)
- 0.26.0+ds-1 (bookworm)