[roll] Roll fuchsia [virtualization][vsock] Fix client initiated shutdown race The current behaviour of the device is to send a SHUTDOWN_BOTH packet from the read write state, but the guest can reply to it (with a RESET) before the state transition finishes which sends the connection to a forced shutdown state. The read write state should only send half shutdown packets (since it can still read or write on the other half), and let the client initiated shutdown state send the full shutdown. Tested: 1) Added a 1s delay between sending shutdown and transitioning between states 2) Ran the Termina vsock integration test 3) Confirmed that the device can mistakenly enter forced shutdown (which sends reset packets back to the guest when it thinks the shutdown was clean) Original-Bug: 97355,107486 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/718084 Original-Revision: b84a1ce38c98311645b706b9cb35c5c57bb41018 GitOrigin-RevId: 1edec733a3d3e65d1573c7196ac781ce88bb658e Change-Id: Icc023a30fef7bf65f63bdff267e87967ba09e21f
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 via the IRC channel #fuchsia on Freenode.
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.