| commit | ea9b79b73a96701295059741002810fe5b3d185d | [log] [tgz] |
|---|---|---|
| author | Charles Celerier <chcl@fuchsia.infra.roller.google.com> | Mon Dec 09 15:49:51 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Dec 09 07:52:51 2024 -0800 |
| tree | 1eb5603f03437c5472ee337dd72f7f5e5698ba61 | |
| parent | deea5223b9f75077edba4e3e78603331c26233b6 [diff] |
[roll] Roll fuchsia [wlan] Verify iface responds to a request before return from CreateIface This change accomplishes two goals: 1. Removes the ambiguity from a return from `CreateIface` and receiving a `fuchsia.wlan.device.service/DeviceWatcher.OnIfaceAdded`. 2. Ensures the caller of `DeviceMonitor.CreateIface` receives an iface that is responsive and not obviously broken. Accomplishing Reason (1) causes `OnIfaceAdded` to take on an informative role rather than a possibly logical one. And we might, after careful consideration, determine `OnIfaceAdded` can be deleted (likely after enforcing a "one client only" policy for `DeviceWatcher`). Reason (2) is desired because interface creation can fail outside the layer handling the `Phy.CreateIface` request. Regardless of which layer serves the `Phy` protocol, all interface creation failures will result in the `GenericSme` channel closing without responding to an initial request. Test: Modified existing tests which verify this change requires reponding to an initial query on a created iface. Original-Bug: 382075991 Original-Fixed: 382051387 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1166934 Original-Revision: b36a426b44a5b7fcf600749f0071786ff05f39f1 GitOrigin-RevId: 802ba6ca5415772c362a8e9b873b645a7d0791ac Change-Id: I3223feda6baed531e030a50e6f55c988b31bc67a
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.