iovisor / iovisor/bcc

bpflist doesn't show attached probes

Open
#4,981 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
5d 13h
Merged PRs (30d)
3

Description

bpflist -vv shows no attached kprobes or uprobes
```
$bpflist -vv
open kprobes:

open uprobes:

PID COMM TYPE COUNT
2718 biolatency map 2
2718 biolatency prog 2
``

I suspect this is because bpflist looks for the probes in debugfs (/sys/kernel/debug/tracing/{k,u}probe_events) and attach_kprobe uses perf_event_open() syscall when available, which is probably always nowadays.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by inspecting bpflist's probe discovery and the attach_kprobe path, comparing debugfs probe listings with the perf_event_open() behavior described in the report. Done means bpflist -vv correctly reports attached kprobes and uprobes while retaining its existing map and program output.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
cli, observability, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.