[roll] Roll fuchsia [lowpan] Implement the ePSKc mode state update with an async way.
The current ePSKc mode update logic (handle_epskc_state_changed) is
running in the same process with the `init_ot` function. The calling
context already holds the `driver_state` lock. When OpenThread ephemeral
key callback is triggered, the handler then attempts to re-acquire the
`driver_state` lock to access the current ePSKc state, resulting in a
deadlock (ReenterMutex) and crash.
This CL fixes the issue by implementing an async send/receive channel
to process the ePSKc mode state updates, it's the similar pattern used
to handle border agent callbacks.
Original-Bug: b/373664917
Test: manual test with Thread Utilities app to verify the overall ePSKc
work flow, works as expected.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1422314
Original-Revision: 68207755fa5e03ac71ec9e5279bc7d7b92699262
GitOrigin-RevId: 0578ff77c76b1a2e183316c4740373085d4248b7
Change-Id: I832bbea9f5a52d46793d297f913a90de037d5276
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.