Skip to content
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

No longer validate Wasm module header in Module::new_unchecked #1025

Merged
merged 4 commits into from May 10, 2024

Conversation

Robbepop
Copy link
Member

@Robbepop Robbepop commented May 9, 2024

Benchmarks showed that validation of the data section can be very costly for some Wasm binaries and furthermore the data section does strictly not belong to the Wasm module header. Therefore it makes sense to no longer validate it in header-only validation mode.

Copy link

codecov bot commented May 9, 2024

Codecov Report

Attention: Patch coverage is 82.00000% with 9 lines in your changes are missing coverage. Please review.

Project coverage is 80.79%. Comparing base (6214e51) to head (c39530e).

Files Patch % Lines
crates/wasmi/src/module/parser.rs 82.00% 9 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1025      +/-   ##
==========================================
+ Coverage   80.77%   80.79%   +0.02%     
==========================================
  Files         269      269              
  Lines       24788    24802      +14     
==========================================
+ Hits        20022    20040      +18     
+ Misses       4766     4762       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Robbepop Robbepop changed the title Do not validate data section in header-only validation mode No longer validate Wasm module header in Module::new_unchecked May 10, 2024
@Robbepop Robbepop merged commit 2e7a28f into master May 10, 2024
17 checks passed
@Robbepop Robbepop deleted the rf-unchecked-data-section branch May 10, 2024 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant