bluetooth: host: fix hang issue caused by 2 consecutive bt disable co… #87611
+2
−1
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
zephyrbot
added
size: XS
zephyrbot
requested review from
alwa-nordic,
cvinayak,
hermabe,
jhedberg,
rugeGerritsen,
sjanc,
Thalley and
theob-pro
Thalley
reviewed
Mar 25, 2025
zhaynxp
force-pushed
the
fix_2_btdisable_hang
branch
2 times, most recently
from
2bf46ee to
6d57c33
Compare
…ands - add BT_DEV_DISABLE flag to BT_DEV_PERSISTENT_FLAGS to protect consecutive bt disable from running Signed-off-by: Ying Zhang <ying.zhang_2@nxp.com>
zhaynxp
force-pushed
the
fix_2_btdisable_hang
branch
from
6d57c33 to
88fd228
Compare
Thalley
approved these changes
Mar 25, 2025
jhedberg
approved these changes
Mar 25, 2025
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.
the bt_dev.flags will be reset to BT_DEV_ENABLE in hci_reset_complete() API which among bt_disable() API, it will clear the previously set BT_DEV_DISABLE flag in the begining of bt_disable() API, and resulting 2nd bt_disable go ahead to execute without BT_DEV_DISABLE flag protection, finally device hang at failed to receive HCI_Reset event in 2nd bt_disable() due to hci->recv was cleared at 1st time bt_disable() called.