Skip to content

JIT/Interpreter and bpf2c pass different options to verifier #4323

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.

Sign up for GitHub

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

Jump to bottom
Open
Alan-Jowett opened this issue Apr 3, 2025 · 1 comment · May be fixed by #4324
Open

JIT/Interpreter and bpf2c pass different options to verifier #4323

Alan-Jowett opened this issue Apr 3, 2025 · 1 comment · May be fixed by #4324
Assignees
@Alan-Jowett
Labels
enhancement New feature or request triaged Discussed in a triage meeting
Milestone
2507

Comments

@Alan-Jowett
Copy link
Member

JIT/Interpreter and bpf2c pass different options to verifier.

This results in slightly different results when the same program is verified for JIT vs when it is verified for bpf2c.
@Alan-Jowett Alan-Jowett linked a pull request Apr 7, 2025 that will close this issue
Open
@Alan-Jowett
Copy link
Member Author

On examination, the differences are only related to what the verifier reports.

@Alan-Jowett Alan-Jowett reopened this Apr 8, 2025
@shankarseal shankarseal added triaged Discussed in a triage meeting enhancement New feature or request labels Apr 14, 2025
@shankarseal shankarseal added this to the 2507 milestone Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Alan-Jowett Alan-Jowett

Labels
enhancement New feature or request triaged Discussed in a triage meeting
Projects
None yet
Milestone
2507
Development

Successfully merging a pull request may close this issue.

JIT and bpf2c use different verifier options Alan-Jowett/ebpf-for-windows
2 participants
@Alan-Jowett @shankarseal