-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
gh-123828: fix data raceing for _waiting_release method in _interpchannelsmodule.c #124107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…erpchannelsmodule.c Signed-off-by: Manjusaka <me@manjusaka.me>
d8a89c1
to
ffee4ed
Compare
@picnixz out of the scope of this PR, but would it be feasible to migrate things using |
Maybe. Haven't had the time to think about it and I don't know if it's possible for every case. Could you open another issue for that? also how would performances / maintenance cost be impacted? |
It's probably worth discussing on discourse before opening an issue. AFAIK, |
@picnixz May I ask if this pr is worth to merge? |
I am not well-versed enough in this part of the code to be sure that it's correct, so I'll let Eric decide (or @ZeroIntensity) |
The core change looks correct, I noticed this with Eric at the sprint. Please add a test though. |
Sorry about this. I have noticed that seems We don't have tests for the data race before(correct me if I'm wrong). You mean that we enable some test in CI? |
Just add something that stresses this concurrently, we'll get around to enabling TSan on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should remove this news entry. _interpchannels
isn't exposed to any user-facing API.
This issue is triggered by TSAN test. So I think if we don't need add more test if we are planning to enable TSAN |
I think @ZeroIntensity wanted add a test that specifically triggers it, not one that indirectly triggers it. |
Signed-off-by: Manjusaka <me@manjusaka.me>
Signed-off-by: Manjusaka <me@manjusaka.me>
@ZeroIntensity @picnixz Actually I think we don't need new tests anymore. In #129824, we found that the current test will triger the TSAN report. And this PR can fix the test and I reenable the test now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, thanks, this looks good.
@ericsnowcurrently This is the race I was telling you about at the sprints. As far as I can tell, this is the only thing blocking test_interpreters
from running on the free-threaded build.
The test has been failed https://buildbot.python.org/#/builders/75/builds/3415 I'm trying to figure it out |
That might be the leak from #139073. |
Any reason not to backport this to 3.14? |
I didn't think it was that big of a deal because |
Thanks @Zheaoli for the PR, and @ZeroIntensity for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
…ythonGH-124107) (cherry picked from commit f39dea3) Co-authored-by: Nadeshiko Manju <me@manjusaka.me>
GH-139517 is a backport of this pull request to the 3.14 branch. |
…GH-124107) (GH-139517) gh-123828: Fix data race in `_interpchannels._waiting_release` (GH-124107) (cherry picked from commit f39dea3) Co-authored-by: Nadeshiko Manju <me@manjusaka.me>
Fix #123828