GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — gh-112723: Call `PyThreadState_Clear()` from the correct interpreter by colesbury · Pull Request #112776 · python/cpython

Conversation

@colesbury

@colesbury colesbury commented Dec 5, 2023 •
edited by bedevere-app Bot
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

The PyThreadState_Clear() function must only be called with the GIL held and must be called from the same interpreter as the passed in thread state. Otherwise, any Python objects on the thread state may be destroyed using the wrong interpreter, leading to memory corruption.

This is also important for Py_GIL_DISABLED builds because object free lists will be associated with PyThreadStates and cleared in PyThreadState_Clear().

This fixes two places that called PyThreadState_Clear() from the wrong interpreter and adds an assertion to PyThreadState_Clear().

The new_interpreter() function required some refactoring so that no calls that may return errors happen between the creation of the thread state and the acquisition of the GIL.

  • Issue: PyThreadState_Clear() should only be called from the same interpreter #112723

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@colesbury
pythongh-112723: Call PyThreadState_Clear() from the correct interp…
ded968d
…reter

The `PyThreadState_Clear()` function must only be called with the GIL
held and must be called from the same interpreter as the passed in
thread state. Otherwise, any Python objects on the thread state may be
destroyed using the wrong interpreter, leading to memory corruption.

This is also important for `Py_GIL_DISABLED` builds because free lists
will be associated with PyThreadStates and cleared in
`PyThreadState_Clear()`.

This fixes two places that called `PyThreadState_Clear()` from the wrong
interpreter and adds an assertion to `PyThreadState_Clear()`.
@colesbury colesbury added topic-subinterpreters 3.13 only security fixes topic-free-threading labels Dec 5, 2023
@colesbury
colesbury requested a review from carljm December 5, 2023 21:23
@colesbury
colesbury requested review from gvanrossum and markshannon as code owners December 5, 2023 21:23
@bedevere-app bedevere-app Bot added the awaiting review label Dec 5, 2023
@bedevere-app bedevere-app Bot mentioned this pull request Dec 5, 2023
PyThreadState_Clear() should only be called from the same interpreter #112723
Closed
@colesbury colesbury added the skip news label Dec 5, 2023
@colesbury

colesbury commented Dec 5, 2023

Copy link
Copy Markdown
Contributor Author

cc @ericsnowcurrently

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@ericsnowcurrently
ericsnowcurrently self-requested a review December 5, 2023 22:25
carljm
carljm reviewed Dec 7, 2023
View reviewed changes
Comment thread Modules/_xxsubinterpretersmodule.c Resolved

Uh oh!

There was an error while loading. Please reload this page.

Comment thread Python/pylifecycle.c Resolved

Uh oh!

There was an error while loading. Please reload this page.

@colesbury colesbury mentioned this pull request Dec 10, 2023
Use per-thread freelists in --disable-gil builds #111968
Closed
@carljm
carljm merged commit a3c0318 into python:main Dec 13, 2023
@bedevere-app bedevere-app Bot removed the awaiting review label Dec 13, 2023
@colesbury
colesbury deleted the PyThreadState_Clear branch January 5, 2024 18:37
aisk pushed a commit to aisk/cpython that referenced this pull request Feb 11, 2024
@colesbury @aisk
pythongh-112723: Call PyThreadState_Clear() from the correct interp…
07a5e7f
…reter (python#112776)

The `PyThreadState_Clear()` function must only be called with the GIL
held and must be called from the same interpreter as the passed in
thread state. Otherwise, any Python objects on the thread state may be
destroyed using the wrong interpreter, leading to memory corruption.

This is also important for `Py_GIL_DISABLED` builds because free lists
will be associated with PyThreadStates and cleared in
`PyThreadState_Clear()`.

This fixes two places that called `PyThreadState_Clear()` from the wrong
interpreter and adds an assertion to `PyThreadState_Clear()`.
Glyphack pushed a commit to Glyphack/cpython that referenced this pull request Sep 2, 2024
@colesbury @Glyphack
pythongh-112723: Call PyThreadState_Clear() from the correct interp…
9efc048
…reter (python#112776)

The `PyThreadState_Clear()` function must only be called with the GIL
held and must be called from the same interpreter as the passed in
thread state. Otherwise, any Python objects on the thread state may be
destroyed using the wrong interpreter, leading to memory corruption.

This is also important for `Py_GIL_DISABLED` builds because free lists
will be associated with PyThreadStates and cleared in
`PyThreadState_Clear()`.

This fixes two places that called `PyThreadState_Clear()` from the wrong
interpreter and adds an assertion to `PyThreadState_Clear()`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@carljm carljm carljm left review comments
@markshannon markshannon Awaiting requested review from markshannon
@gvanrossum gvanrossum Awaiting requested review from gvanrossum
@ericsnowcurrently ericsnowcurrently Awaiting requested review from ericsnowcurrently ericsnowcurrently is a code owner

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

3.13 only security fixes skip news topic-free-threading topic-subinterpreters

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@colesbury @carljm
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.