gh-127165: Disallow embedded NULL characters in _interpreters
#127199
+9
−0
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.
Currently, null characters in shared namespaces cause truncation of the actual string, because it's eventually passed to
PyUnicode_FromString
, which uses thestrlen
instead of the actual size. Then, things break because the string unexpectedly is not in the namespace dictionary. This fixes that by just raising if we find an embedded NULL character in_copy_string_obj_raw
.We could support embedded NULLs by storing the size alongside the name, but this is much simpler (and in practice, nobody is trying to name variables containing
\x00
).concurrent.futures.interpreter.WorkerContext
#127165