Issues: microsoft/ebpf-for-windows
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Investigate hang caused by missed WFP 'filter delete' confirmation callback invocation.
bug
Something isn't working
bpf_map_lookup_batch: Add test cases to fetch data in batches
bug
Something isn't working
#3565
opened May 21, 2024 by
shpalani
[bpf_map_lookup_batch map api]: Crash in BPF_MAP_TYPE_PERCPU_HASH map type during batch operation
bug
Something isn't working
#3564
opened May 21, 2024 by
shpalani
bpf_map_lookup_batch map api: Fails to fetch all entries, when the next key is deleted in the hash map.
bug
Something isn't working
#3561
opened May 21, 2024 by
shpalani
Add support for autoload libbpf APIs
enhancement
New feature or request
triaged
Discussed in a triage meeting
Support BPF dynamic pointers
blocked
Blocked on another issue that must be done first
enhancement
New feature or request
help wanted
Extra attention is needed
triaged
Discussed in a triage meeting
Add versioning in the native module NMR structs
enhancement
New feature or request
P2
triaged
Discussed in a triage meeting
Fuzzing the verifier using debugging builds is inefficient
blocked
Blocked on another issue that must be done first
optimization
Affects perf but not correctness or applicability
P2
tests
triaged
Discussed in a triage meeting
Scheduled eBPF release is due
P1
release
Issue/task related to release process.
triaged
Discussed in a triage meeting
Workflow failed - user_mode_multi_threaded_stress
bug
Something isn't working
ci/cd
Issue is specific to CI/CD
triaged
Discussed in a triage meeting
Change current NuGet account to Microsoft account & prefix.
enhancement
New feature or request
nuget update
P3
triaged
Discussed in a triage meeting
libfuzzer based fuzzer's aren't covering all code paths
enhancement
New feature or request
tests
triaged
Discussed in a triage meeting
Workflow failed - km_mt_stress_tests
bug
Something isn't working
ci/cd
Issue is specific to CI/CD
P1
triaged
Discussed in a triage meeting
The function ebpf_program_execute_test_run should more closely align with real usage.
enhancement
New feature or request
P2
tests
triaged
Discussed in a triage meeting
Version of bpf_conformance tool should be stored in single location
cleanup
Affects API usability or code maintainability but not correctness or applicability
P2
triaged
Discussed in a triage meeting
Ideally the downlevel tests would be a matrix of supported versions.
enhancement
New feature or request
P3
tests
triaged
Discussed in a triage meeting
bpf2c should support bpf2bpf function calls
blocked
Blocked on another issue that must be done first
enhancement
New feature or request
triaged
Discussed in a triage meeting
update-release-version.ps1
should have an option to commit the changes if build is successful.
enhancement
The CI/CD release validation work flows must run the non-deterministic tests multiple times in a loop.
ci/cd
Issue is specific to CI/CD
enhancement
New feature or request
P2
tests
triaged
Discussed in a triage meeting
Check for clang version in bpf2c / ebpfapi.dll
enhancement
New feature or request
P2
triaged
Discussed in a triage meeting
Add script for executing a command against a given list of VMs associated with self host runners
ci/cd
Issue is specific to CI/CD
enhancement
New feature or request
help wanted
Extra attention is needed
triaged
Discussed in a triage meeting
Self-host runner information should be provided as per-repository configuration data.
ci/cd
Issue is specific to CI/CD
enhancement
New feature or request
P2
triaged
Discussed in a triage meeting
Workflow failed - km_mt_stress_tests_restart_extension
bug
Something isn't working
ci/cd
Issue is specific to CI/CD
P1
triaged
Discussed in a triage meeting
Previous Next
ProTip!
Follow long discussions with comments:>50.