ebpf-verifier (prevail) is out of date
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 73
- Forks
- 23
- Avg merge
- 21h 17m
- Merged PRs (30d)
- 1
Description
Describe the bug
The ebpf-verifier submodule used in jbpf is >2 years of out date (last commit is December 2022). Since then, ebpf-verifier (now named prevail) has made several important bug fixes that impact verification correctness. It's also added more useful errors upon verification failure and line numbers where verification failed.
To Reproduce
Steps to reproduce the behavior:
- Run jbpf-verifier-cli against a bpf program
- Receive verification errors that no longer exist in upstream prevail, or errors that are tough to debug without error context and line numbers
Expected behavior
Update ebpf-verifier in jbpf. I spent some time trying this out, but ran into a lot of issues especially with the whole project rename scheme (ebpf-verifier => prevail).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the jbpf-verifier-cli entry point and inspect how the ebpf-verifier submodule is referenced. Compare the current submodule with upstream prevail, accounting for the project rename; the work is done when jbpf uses the updated verifier and exposes its corrected errors and verification line numbers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100