[roll] Roll fuchsia [vsock] Fix attempting to connect to VMADDR_CID_LOCAL without loopback

This makes the logic to determine if a CID is supported consistent with
the logic used to pick a device so that attempting to connect to a cid
with no backing device results in a connection refusal instead of a
vsock service panic.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1254966
Original-Revision: f0843b95f66d8b944ba842f9bd95f89f6a5308e8
GitOrigin-RevId: 485419aa94202dacedb0210fca285c2697cfdc07
Change-Id: I6222c0b66d9457b9c31c825883d4837639a5c30d
1 file changed
tree: 53be5479ae26e62e96ddbc9e4af926701da307d7
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.