RFCOMM: Handle packets received before DLC sink set #483
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
zxzxwu
changed the title
zxzxwu
force-pushed
the
rfc
branch
3 times, most recently
from
f169b42
to
25dedf4
Compare
barbibulle
reviewed
May 7, 2024
barbibulle
reviewed
May 9, 2024
zxzxwu
changed the title
barbibulle
approved these changes
May 10, 2024
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.
This race condition is not common since usually the initiator (no matter it's an L2CAP or RFCOMM channel) should send the first packet. However, in HFP, if it is AG opening the channel, AG cannot send the first packet, and HF may send AT+BRSF too quick that
open_dlc()haven't returned yet.