-
Notifications
You must be signed in to change notification settings - Fork 5
libbpf: Add debug messaging in dedup equivalence/identity matching #6455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: bpf-next_base
Are you sure you want to change the base?
libbpf: Add debug messaging in dedup equivalence/identity matching #6455
Conversation
|
Upstream branch: ff34657 |
52f5a27 to
037d2fc
Compare
|
Upstream branch: ff34657 |
e8226a2 to
e0b8cfe
Compare
037d2fc to
8f722b4
Compare
|
Upstream branch: 8f7aa3d |
e0b8cfe to
a70fcdd
Compare
8f722b4 to
03e2ed2
Compare
|
Upstream branch: 835a507 |
a70fcdd to
4cbf57b
Compare
03e2ed2 to
3ea267d
Compare
|
Upstream branch: 835a507 |
4cbf57b to
f4269c4
Compare
3ea267d to
6d4eb64
Compare
We have seen a number of issues like [1]; failures to deduplicate key kernel data structures like task_struct. These are often hard to debug from pahole even with verbose output, especially when identity/equivalence checks fail deep in a nested struct comparison. Here we add debug messages of the form libbpf: STRUCT 'task_struct' size=2560 vlen=194 cand_id[54222] canon_id[102820] shallow-equal but not equiv for field#23 'sched_class': 0 These will be emitted during dedup from pahole when --verbose/-V is specified. This greatly helps identify exactly where dedup failures are experienced. [1] https://lore.kernel.org/bpf/[email protected]/ Changes since v1: - updated debug messages to refer to shallow-equal, added ids (Andrii) Signed-off-by: Alan Maguire <[email protected]>
|
Upstream branch: 835a507 |
f4269c4 to
8546e36
Compare
Pull request for series with
subject: libbpf: Add debug messaging in dedup equivalence/identity matching
version: 2
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1030217