fix(libc): avoid undefined memcpy in js_worker_postMessage with len==0#1483
Open
andreasrosdal wants to merge 1 commit into
Open
fix(libc): avoid undefined memcpy in js_worker_postMessage with len==0#1483andreasrosdal wants to merge 1 commit into
andreasrosdal wants to merge 1 commit into
Conversation
memcpy(dst, src, 0) is UB per C11 7.21.1 when either pointer is NULL, even if no bytes are copied — UBSan with -fsanitize=nonnull-attribute flags it and a strict optimiser may exploit the implied non-NULL attribute to elide subsequent NULL checks. In practice JS_WriteObject2 always emits a non-empty buffer, but make the call site safe by hand so the worker pipe is robust to any future serializer change. No test: triggering the UB requires data_len == 0 and malloc(0) returning non-NULL, which doesn't happen on the current writer. UBSan in CI would catch a regression.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
memcpy(dst, src, 0) is UB per C11 7.21.1 when either pointer is NULL, even if no bytes are copied — UBSan with -fsanitize=nonnull-attribute flags it and a strict optimiser may exploit the implied non-NULL attribute to elide subsequent NULL checks.
In practice JS_WriteObject2 always emits a non-empty buffer, but make the call site safe by hand so the worker pipe is robust to any future serializer change.
No test: triggering the UB requires data_len == 0 and malloc(0) returning non-NULL, which doesn't happen on the current writer. UBSan in CI would catch a regression.