Remove --no-verify option from bpf2c #3571
Labels
cleanup
Affects API usability or code maintainability but not correctness or applicability
good first issue
Good for newcomers
P2
triaged
Discussed in a triage meeting
Milestone
Describe the feature you'd like supported
Originally this option was added to improve coverage of the bpf2c code generation, around features bpf2c supported but the verifier didn't support yet (things like atomics) but those are now supported so this isn't needed any more. Leaving the option to generate knowingly unsafe code is bad for seurity and so this should be removed.
Proposed solution
Remove the --no-verify option.
Additional context
No response
The text was updated successfully, but these errors were encountered: