| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The libc setpwent, getpwent, and endpwent functions are not thread-safe. Protect them with mutexs in free-threading builds.
There was a problem hiding this comment.
We need a critical section here. Py_CLEAR and Py_DECREF are re-entrant (as in, they can invoke the eval loop), so a mutex is prone to lock-ordering or re-entrancy deadlocks.
Sorry, something went wrong.
|
Actually, sorry, we need to fix subinterpreter thread-safety here too. We can't do that with a critical section. Could you adjust the mutex to go over solely the libc calls? |
Sorry, something went wrong.
Hmm, yeah, good point. I guess we can just defer the decrefs until exit. |
Sorry, something went wrong.
…ility of re-entrancy.
… they are strongly referenced by that, so we can dec-ref them safely.
| Back | FazBrowse Home | New Git URL |
The libc setpwent, getpwent, and endpwent functions are not thread-safe. Protect them with mutexs in free-threading builds.