Skip to content
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

gc: fix a potential deadlock #6112

Merged
merged 1 commit into from
Mar 21, 2019
Merged

gc: fix a potential deadlock #6112

merged 1 commit into from
Mar 21, 2019

Conversation

Stebalien
Copy link
Member

Events:

  1. User triggers a GC.
  2. User aborts the GC.
  3. We fail to delete a block when the output channel is already full.

This is really unlikely to happen in practice but it's still incorrect.

Could be related to #6107.

Events:

1. User triggers a GC.
2. User aborts the GC.
3. We fail to delete a block when the output channel is already full.

This is really unlikely to happen in practice but it's still incorrect.

Could be related to #6107

License: MIT
Signed-off-by: Steven Allen <steven@stebalien.com>
@Stebalien Stebalien requested a review from Kubuxu as a code owner March 21, 2019 02:17
@ghost ghost assigned Stebalien Mar 21, 2019
@ghost ghost added the status/in-progress In progress label Mar 21, 2019
@Stebalien Stebalien merged commit c0c6827 into master Mar 21, 2019
@Stebalien Stebalien deleted the fix/gc-deadlock branch March 21, 2019 04:52
@ghost ghost removed the status/in-progress In progress label Mar 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants