Jon Shallow b75c784a20 Constrained Stack: No need for individual locks ...

If a proxy reads in a packet via coap_read_endpoint, which then
invokes an ongoing proxy TCP connection, while waiting for the CSM
response of the new session, coap_read_endpoint would get invoked
again if there is any data to read on any of the listening endpoints..

With a Constrained Stack, the read in data is protected by mutex
m_read_enpoint - which is still locked when trying to wait for the
CSM.

As the code is either single threaded, or protected by global_lock
if multi-threaded, there is no need to maintain mutexes such as
m_read_endpoint.  This PR removes these not needed mutexes.

2024-07-22 08:47:05 +01:00

..

coap3

Constrained Stack: No need for individual locks

2024-07-22 08:47:05 +01:00

oscore

pre-commit: Include re-styled OSCORE files to checks

2023-07-05 10:50:25 +01:00