gattrib: Fix a request/response command deadlock New requests and responses are never sent if a request was sent and the response for it hasn't been received yet. As a result, if both end points send requests at the same time, a deadlock could occur. This could happen, for instance, if the client sends a read request and the server sends an indication before responding to the read request. Fix this by introducing an additional queue for responses. Responses may be sent while there's still a pending request/indication.

Diffstat

1 files changed, 87 insertions(+), 24 deletions(-)