-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make sure we handle BUSY responses during CASE properly. (#28901)
If we got a BUSY response during a CASE handshake and successfully read the wait time, we would treat that as a success case, not a failure case, and not realize that our exchange has been closed. That could lead to use-after-free when we later tried to abort an already-closed exchange. The problem was introduced in 59a0b2f (PR #28153). The new unit test fails (both with ASAN failures and with incorrect state because the client that got BUSY does not think the handshake failed) without this fix.
- Loading branch information
1 parent
caa44e8
commit 1223544
Showing
2 changed files
with
83 additions
and
25 deletions.
There are no files selected for viewing
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
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