[roll] Roll fuchsia [netstack3] Reduce lock acquisition in TCP bind Do a little bit less work while under lock performing the bind operation. We can resolve the local address by going into the IP layer before acquiring the demux lock. Unlike connect, bind has a more natural 4th match arm for the case where the socket is bound to both stacks so keep that around. Remove the context functions that allowed accessing the demux state and the IP layer at the same time. Original-Fixed: 327489613, 327488712 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1074552 Original-Revision: dc0a8c7a4ec05dd03a73bdb79d613d1ac67e1535 GitOrigin-RevId: 13119920e084dac96bcdcaee6797bdf41b84196f Change-Id: Ia6ace72dd67194f53a67567eeb53f5e19a39db7e
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.