-
Notifications
You must be signed in to change notification settings - Fork 928
fix: Deadlock and race in peer
, test improvements
#3086
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
eaacbca
fix: Potential deadlock in peer.Channel dc.OnOpen
mafredri 5b5dde9
fix: Potential send on closed channel
mafredri 8061d4c
fix: Improve robustness of waitOpened during close
mafredri 077b02e
chore: Simplify statements
mafredri 0474aa9
fix: Improve teardown and timeout of peer tests
mafredri 5e33a9a
fix: Improve robustness of TestConn/Buffering test
mafredri ca349ca
Update peer/channel.go
mafredri 445e8b0
chore: Re-introduce re-check comment
mafredri File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
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.
Why do we need this check? Is it a problem if
sendMore
gets a value in the buffered channel? I don't think it matters which one is prioritized. Either one will exit the select statement and "return". IfsendMore
is sent a write will happen. But if you close the connection, a write will also happen because the<-c.sendMore
gets unblocked.Idk, just seems redundant.
Grabbing the closed lock doesn't seem necessary because of the same argument.
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.
Both (check and mutex) are needed because
c.sendMore
is closed inc.closeWithError
, so we want to guard against potentially sending on a closed channel (which would panic).By holding the mutex, we ensure that closure doesn't happen between the
isClosed()
check and send onc.sendMore
.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.
Oh btw, I was also first of the impression that the check might not be needed, but without it the
pion/sctp
library may try to unlock an unlocked mutex: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.
Will a select send something on a closed channel? If so TIL.
👍
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.
Yup, if you try to run this playground a couple of times, you will notice that sometimes it exits 0, and sometimes panics: https://go.dev/play/p/c35kE0948kl