Skip to content

l2cap: do not invoke the connection callback more than once - #15

Merged
mardy merged 1 commit into
masterfrom
no-duplicate-callbacks
Nov 4, 2026
Merged

mardy merged 1 commit into
masterfrom
no-duplicate-callbacks

Conversation

@mardy

@mardy mardy commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

This code path can be triggered if we have open than one L2CAP channel on the same ACL connection: the first gets connected without authentication, then for the second one we request authentication but it fails: in this case the acl_connected_cb() function would also invoke the connection callback on the first L2CAP channel, using a callback pointer which might be no longer valid.

This code path can be triggered if we have open than one L2CAP channel
on the same ACL connection: the first gets connected without
authentication, then for the second one we request authentication but it
fails: in this case the acl_connected_cb() function would also invoke
the connection callback on the first L2CAP channel, using a callback
pointer which might be no longer valid.
@mardy
mardy merged commit 6bb4fd9 into master Nov 4, 2026
4 checks passed
@mardy
mardy deleted the no-duplicate-callbacks branch November 4, 2026 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant