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.

Sign up for GitHub

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

Jump to bottom

Bluetooth: CCC values should be treated as bitfields #81004

Open
alwa-nordic opened this issue Nov 6, 2024 · 0 comments
Open

Bluetooth: CCC values should be treated as bitfields #81004

alwa-nordic opened this issue Nov 6, 2024 · 0 comments
Assignees
@jhedberg @alwa-nordic
Labels
area: Bluetooth Host area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@alwa-nordic
Copy link
Collaborator

See #80988 (comment).

A CCC value is a bitfield. When testing for BT_GATT_CCC_NOTIFY and BT_GATT_CCC_INDICATE, & should be used instead of ==.

This issue is about all misuses like this. Some may be benign, but this issue is labeled 'bug' because it's likely some instances may be a bug that can be triggered in a multiple connection scenario.

More info the comment thread linked above. This issue is to be refined.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhedberg jhedberg

@alwa-nordic alwa-nordic

Labels
area: Bluetooth Host area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jhedberg @alwa-nordic