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.

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

[nrf fromtree] Bluetooth: att: don't re-use the ATT buffer for confir… #1335

Merged
merged 1 commit into from
Oct 6, 2023

Commits on Oct 6, 2023

  1. [nrf fromtree] Bluetooth: att: don't re-use the ATT buffer for confir…

    …mations
    
    If the peer is a zephyr host, there is no problem, as the Zephyr
    host limits sending parallel REQs and INDs.
    
    But the spec allows sending those in parallel, and it may end up that
    the re-used REQ buffer hasn't been destroyed when an indication comes.
    
    Only re-use the buffer when enqueuing ATT responses.
    
    This means that we may run out of buffers if the peer sends too many
    indications and our application also sends a lot of commands/notifications.
    
    The rationale for this is that having to handle a lot of requests is a
    more plausible scenario (e.g. being discovered by multiple peers) than
    handling lots of parallel indications.
    
    Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no>
    (cherry picked from commit 7093538)
    jori-nordic committed Oct 6, 2023
    Configuration menu
    Copy the full SHA
    957f48d View commit details
    Browse the repository at this point in the history