-
Notifications
You must be signed in to change notification settings - Fork 19
Adds Frama-C WP proofs #272
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
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
2ab2ace
Clamp FUSE read replies to the requested size
jserv f569283
Bound GDB stub reads running past the packet terminator
jserv 3915b9a
Validate program header geometry at both ELF parse sites
jserv 8bc4915
Reject PT_LOAD extents that wrap the address space
jserv 7dbd9e3
Ignore PT_LOAD segments that map no bytes
jserv d0e912b
Derive AT_PHDR from the PT_LOAD that carries the table
jserv 988ecdb
Reject overflowing load extents before execve's point of no return
jserv 869a7d6
Map segments from the recorded parse, and relocate through a window
jserv 4867d2c
Split elf_load_fd's program header loop
jserv 749c794
Clamp available bytes to the end of the primary buffer
jserv b5ad6b9
CI: bump actions/cache to v6
jserv 47b96bd
Prove the ELF parsing core with Frama-C WP
jserv 11d71ae
Extract and prove the guest address arithmetic
jserv 47cf984
Prove the GDB RSP hex and checksum helpers
jserv a83af2f
Disable Infer's uninitialized-value checker
jserv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| { | ||
| "disable-issue-type": ["PULSE_UNINITIALIZED_VALUE"] | ||
| } | ||
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: This .inferconfig disables the PULSE_UNINITIALIZED_VALUE checker for the entire project, not just the one false-positive path. The workflow comment documents that 135 findings were audited and all callers check the return value, but that audit only holds for the current snapshot; any genuinely uninitialized read introduced anywhere in the codebase after this merge will no longer be caught by the gating Infer step. Consider a more surgical scope instead of a global disable — for example a file/pattern-scoped suppression in .inferconfig or per-function suppression near the chunked-copy path — so the rest of the codebase keeps this memory-safety check. If a global disable is intentional, tracking it in an issue with a follow-up trigger (e.g. when Infer models chunked copies, per the workflow comment) would make the residual risk explicit.
Prompt for AI agents