[roll] Roll fuchsia [virtualization][vsock] Serialize the TX queue

Prior to this change we were using try_for_each_concurrent on the TX
stream purely for convenience, as the guest initiated connection
futures would block and keep polling to remove the connection when
finished.

This is a problem when these connections acquire async locks as ordering
isn't maintained once the writer wakes up after the readers are aborted.
There is no performance hit here, as every TX packet can be immediately
handled due to the credit system.

Original-Bug: 97355

Tested:
1) (With fxr/703363 patched in) Paved this change to a NUC
2) Booted termina via the UI

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/703364
Original-Revision: cf2d3167b8c7c02b67879b024b2f3b2004453179
GitOrigin-RevId: 593784d0d27e1538f83598f001486ad000aa9ebf
Change-Id: I531d4dae2e914c96327af459a3f969434a3eb165
1 file changed
tree: 62315ab8cd46f7441c2b9b5788e92c32d322b8a8
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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 via the IRC channel #fuchsia on Freenode.

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.