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
$ go test -v -run=TestVMNegateA .
=== RUN TestVMNegateA
--- FAIL: TestVMNegateA (0.00s)
vm_bpf_test.go:120: output byte count does not match:
- go: 0
- os: 5
vm_bpf_test.go:124: Go BPF and OS BPF packet outputs do not match
FAIL
exit status 1
FAIL golang.org/x/net/bpf 0.002s
Same logic seems to apply when subtraction brings the register results below zero. Will keep working on this and try to submit a CL to enable this functionality in the near future.
Using this as a tracking issue to see if it's feasible to allow
bpf.NegateA
to be processed by thebpf.VM
type.My research thus far shows that the BPF VM treats any negative result as "return all bytes".
Here's the test I'm writing:
And the results using the current VM:
Same logic seems to apply when subtraction brings the register results below zero. Will keep working on this and try to submit a CL to enable this functionality in the near future.
/cc @danderson
The text was updated successfully, but these errors were encountered: