alexcrichton opened PR #10164 from alexcrichton:fix-fuzz-oom
to bytecodealliance:main
:
Our
StoreLimits
implementation doesn't take into account the reservation of linear memory that it can grow into. This works fine formmap
since memory isn't committed, but it doesn't work in fuzzing for malloc-based memories because the fuzzing harness just thinks a huge allocation is being made and declares OOM. This is fixed in this commit by ensuring that thememory-reservation-for-growth
parameter is tuned smaller-than-the-default-2G when malloc-based memories are used.<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested fitzgen for a review on PR #10164.
alexcrichton requested wasmtime-fuzz-reviewers for a review on PR #10164.
github-actions[bot] commented on PR #10164:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "fuzzing"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
fitzgen submitted PR review.
fitzgen merged PR #10164.
Last updated: Feb 28 2025 at 01:30 UTC