Fix utimensat to avoid passing uninitialized values into WASI calls. #291
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.
Previously, utimensat would leave the mtim and/or atim timestamps
uninitialized when the
MTIM_NOWorATIM_NOWwere in use, becausethat means the respective timestamps are not used.
However, clang now automatically adds
noundefto the arguments infunctions like
__wasi_path_filestat_set_times, and there are caseswhere simplifycfg can see paths where the uninitialized values are
passed to those
noundefarguments.To fix this, change the utimens code to zero out the timestamps when
they aren't in use, to avoid passing uninitialized arguments.