Race between partial_vectorcall_fallback
and _PyVectorcall_FunctionInline
under free-threading
#128050
Labels
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
topic-free-threading
type-bug
An unexpected behavior, bug, or error
Bug report
Bug description:
Repro:
Run the following Python code under v3.13.1t with thread-sanitizer enabled.
Get:
partial_vectorcall_fallback
setsvectorcall
to nullptr if it decides to fall back to a non-vectorcall code path:cpython/Modules/_functoolsmodule.c
Line 366 in b92f101
But this races with the code that reads an object's
vectorcall
in the core function call code:cpython/Include/internal/pycore_call.h
Line 128 in b92f101
CPython versions tested on:
3.13
Operating systems tested on:
Linux
The text was updated successfully, but these errors were encountered: