Skip to content

Conversation

@Mirlenko
Copy link

@Mirlenko Mirlenko commented Feb 27, 2025

The buffer allocation in conn.c will trigger warnings if we try to use anything else than K_NO_WAIT for the timeout when called from within the system workqueue.

The calls in l2cap.c and att.c which may pass non-zero timeouts already have proper handling for failed allocations, so make sure we use K_NO_WAIT to avoid unnecessary warnings from conn.c.

Signed-off-by: Aleksandr Mirlenko [email protected]
(cherry picked from commit 05b16b9)

@Mirlenko Mirlenko force-pushed the fix_buffer_allocation_warnings_in_system_workquue branch from 638c39c to a9695c5 Compare February 27, 2025 09:42
@Mirlenko Mirlenko changed the title Bluetooth: Host: Fix buffer allocation warnings in system workqueue [nrf fromtree] Bluetooth: Host: Fix buffer allocation warnings in system workqueue Feb 27, 2025
…tem workqueue

The buffer allocation in conn.c will trigger warnings if we try to use
anything else than K_NO_WAIT for the timeout when called from within the
system workqueue.

The calls in l2cap.c and att.c which may pass non-zero timeouts already
have proper handling for failed allocations, so make sure we use K_NO_WAIT
to avoid unnecessary warnings from conn.c.

Signed-off-by: Johan Hedberg <[email protected]>
Signed-off-by: Aleksandr Mirlenko <[email protected]>
(cherry picked from commit 05b16b9)
@Mirlenko Mirlenko force-pushed the fix_buffer_allocation_warnings_in_system_workquue branch from a9695c5 to d216dad Compare February 27, 2025 09:56
@rlubos rlubos merged commit b70deaa into nrfconnect:main Feb 27, 2025
17 checks passed
@Mirlenko Mirlenko deleted the fix_buffer_allocation_warnings_in_system_workquue branch February 27, 2025 15:04
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.

5 participants