microsoft / microsoft/ebpf-for-windows

Annotate libbpf API's with _Must_inspect_result_

Open
#1,577 0 comments 0 reactions 0 assignees View on GitHub
enhancement help wanted triaged
Dominant language
C
Stars
3.6k
Forks
311
Avg merge
6d 10h
Merged PRs (30d)
21

Description

The libbpf API's use an int to signal success or failure. We should add _Must_inspect_result_ to help catch bugs where callers potentially ignore failures.

Contributor guide

Open the contributing guide

Research direction

Locate the libbpf API declarations and any existing _Must_inspect_result_ annotation conventions first; the issue does not name specific files or tests. Identify the in-scope APIs that use int for success or failure, then verify that the annotations are applied consistently and that the project still builds and tests successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
api
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.