Title: Py_(X)SETREF should have atomic versions on free-threaded builds · Issue #150044 · python/cpython · GitHub
Open Graph Title: Py_(X)SETREF should have atomic versions on free-threaded builds · Issue #150044 · python/cpython
X Title: Py_(X)SETREF should have atomic versions on free-threaded builds · Issue #150044 · python/cpython
Description: Feature or enhancement Proposal: Right now, Py_SETREF is implemented in non-atomic terms, which makes it subject to operation reordering issues on weakly ordered architectures (which caused a problem fixing gh-149816, where even switchin...
Open Graph Description: Feature or enhancement Proposal: Right now, Py_SETREF is implemented in non-atomic terms, which makes it subject to operation reordering issues on weakly ordered architectures (which caused a probl...
X Description: Feature or enhancement Proposal: Right now, Py_SETREF is implemented in non-atomic terms, which makes it subject to operation reordering issues on weakly ordered architectures (which caused a probl...
Opengraph URL: https://github.com/python/cpython/issues/150044
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Py_(X)SETREF should have atomic versions on free-threaded builds","articleBody":"# Feature or enhancement\n\n### Proposal:\n\nRight now, `Py_SETREF` is implemented in non-atomic terms, which makes it subject to operation reordering issues on weakly ordered architectures (which caused a problem fixing gh-149816, where even switching from separate `Py_CLEAR` and later assignment to `set_sni_cb` to a single \"atomic\" `Py_SETREF` didn't fix the issue on ARM, because SSL's callback was being invoked asynchronously).\n\n`Py_SETREF` is naturally implemented in terms of an atomic exchange, and at least for the free-threaded builds, it seems like it should be implemented as such to avoid such raciness, supplementing the existing:\n\n```c\n#ifdef _Py_TYPEOF\n#define Py_SETREF(dst, src) \\\n do { \\\n _Py_TYPEOF(dst)* _tmp_dst_ptr = \u0026(dst); \\\n _Py_TYPEOF(dst) _tmp_old_dst = (*_tmp_dst_ptr); \\\n *_tmp_dst_ptr = (src); \\\n Py_DECREF(_tmp_old_dst); \\\n } while (0)\n#else\n#define Py_SETREF(dst, src) \\\n do { \\\n PyObject **_tmp_dst_ptr = _Py_CAST(PyObject**, \u0026(dst)); \\\n PyObject *_tmp_old_dst = (*_tmp_dst_ptr); \\\n PyObject *_tmp_src = _PyObject_CAST(src); \\\n memcpy(_tmp_dst_ptr, \u0026_tmp_src, sizeof(PyObject*)); \\\n Py_DECREF(_tmp_old_dst); \\\n } while (0)\n#endif\n\n// Similarly long nonsense for Py_XSETREF\n```\n\nwith a new atomic-based approach for free-threaded builds:\n\n```c\n#define Py_SETREF(dst, src) Py_DECREF(_Py_atomic_exchange_ptr(\u0026(dst), (src)))\n#define Py_XSETREF(dst, src) Py_XDECREF(_Py_atomic_exchange_ptr(\u0026(dst), (src)))\n```\n\nPlease poke holes in this approach. I have a lot of experience with writing multithreaded C code, but will never be convinced I've covered every race condition no matter how simple the code.\n\n### Has this already been discussed elsewhere?\n\nNo response given\n\n### Links to previous discussion of this feature:\n\n_No response_","author":{"url":"https://github.com/MojoVampire","@type":"Person","name":"MojoVampire"},"datePublished":"2026-05-19T00:36:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/150044/cpython/issues/150044"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:c101b103-892b-3876-24c6-f8f6b22d2b4d |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9276:1AC24:1252318:1AC4BC7:6A56208E |
| html-safe-nonce | 2b37ac27fb5a35ce9a2d7fb229d3136017baaa993b729a79e7f2e4f5f164ec08 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5Mjc2OjFBQzI0OjEyNTIzMTg6MUFDNEJDNzo2QTU2MjA4RSIsInZpc2l0b3JfaWQiOiI0MTkxMTYyMDE0MTYzNjczMjMwIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 6d1d82ef4f49f4e2b4065d45f6ed3499a1ee070e47ce1e07c985135b23d743ba |
| hovercard-subject-tag | issue:4473538471 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python/cpython/150044/issue_layout |
| twitter:image | https://opengraph.githubassets.com/fd1a17c60f835cc8ac2b378af03d8910a0c32d6a95d96c49b5c1dde9a343c63f/python/cpython/issues/150044 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/fd1a17c60f835cc8ac2b378af03d8910a0c32d6a95d96c49b5c1dde9a343c63f/python/cpython/issues/150044 |
| og:image:alt | Feature or enhancement Proposal: Right now, Py_SETREF is implemented in non-atomic terms, which makes it subject to operation reordering issues on weakly ordered architectures (which caused a probl... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | MojoVampire |
| hostname | github.com |
| expected-hostname | github.com |
| None | eeb71977be324ce2bc7c4afd597296b8e3527d8922ad94632edd7a7296f8031b |
| turbo-cache-control | no-preview |
| go-import | github.com/python/cpython git https://github.com/python/cpython.git |
| octolytics-dimension-user_id | 1525981 |
| octolytics-dimension-user_login | python |
| octolytics-dimension-repository_id | 81598961 |
| octolytics-dimension-repository_nwo | python/cpython |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 81598961 |
| octolytics-dimension-repository_network_root_nwo | python/cpython |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 3e7957744c8a44d05ff1e464dc5d119e60b98fae |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width