-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
fix deadlock on nested DropHelper #15322
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
⏱️ 3h 12m total CI duration on this PR
|
ibalajiarun
changed the title
fix deadlock on dested DropHelper
fix deadlock on nested DropHelper
Nov 19, 2024
msmouse
force-pushed
the
1119-alden-fix-nested-drop
branch
2 times, most recently
from
November 19, 2024 23:33
e5f9bc0
to
265c821
Compare
ibalajiarun
approved these changes
Nov 19, 2024
grao1991
approved these changes
Nov 19, 2024
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
vusirikala
reviewed
Nov 20, 2024
pub fn wait_for_backlog_drop(&self, no_more_than: usize) { | ||
let _timer = TIMER.timer_with(&[self.name, "wait_for_backlog_drop"]); | ||
self.num_tasks_tracker.wait_for_backlog_drop(no_more_than); | ||
} | ||
|
||
fn schedule_drop_impl<V: Send + 'static>(&self, v: V, notif_sender_opt: Option<Sender<()>>) { | ||
if IN_ANY_DROP_POOL.get() { | ||
drop(v); |
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.
Don't we have to notifier the sender in notif_sender_opt
in this case?
msmouse
force-pushed
the
1119-alden-fix-nested-drop
branch
from
November 20, 2024 00:35
265c821
to
4644351
Compare
This was referenced Nov 20, 2024
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
✅ Forge suite
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
When droping is slow and
DropHelper
s are nested,AsyncConcurrentDropper::schedule_drop()
can deadlock onself.num_tasks_tracker.inc();
How Has This Been Tested?
added unit test, verified failing before fix
Key Areas to Review
Type of Change
Which Components or Systems Does This Change Impact?