You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dthaler opened this issue
Feb 1, 2023
· 0 comments
Assignees
Labels
blockedBlocked on another issue that must be done firstcleanupAffects API usability or code maintainability but not correctness or applicabilitytriagedDiscussed in a triage meeting
vbpf/ebpf-verifier#441 prevents verifying programs with loops.
PR #1991 puts a workaround in place in 3 sample programs.
This issue is to track removing the workaround once the verifier limitation is addressed.
Samples pass verification without the workaround in place.
Actual outcome
Samples fail verification without the workaround in place.
Additional details
No response
The text was updated successfully, but these errors were encountered:
dthaler
added
bug
Something isn't working
cleanup
Affects API usability or code maintainability but not correctness or applicability
blocked
Blocked on another issue that must be done first
and removed
bug
Something isn't working
labels
Feb 1, 2023
dthaler
changed the title
Remove workarounds for verifier limitation once fixed
Remove workarounds for verifier loop limitation once fixed
Nov 25, 2024
blockedBlocked on another issue that must be done firstcleanupAffects API usability or code maintainability but not correctness or applicabilitytriagedDiscussed in a triage meeting
Describe the bug
vbpf/ebpf-verifier#441 prevents verifying programs with loops.
PR #1991 puts a workaround in place in 3 sample programs.
This issue is to track removing the workaround once the verifier limitation is addressed.
Sample programs affected:
bindmonitor.c
bindmonitor_tailcall.c
map.c
OS information
No response
Steps taken to reproduce bug
Try to verify sample programs with loops.
Expected behavior
Samples pass verification without the workaround in place.
Actual outcome
Samples fail verification without the workaround in place.
Additional details
No response
The text was updated successfully, but these errors were encountered: