[roll] Roll fuchsia [netstack3] Stop using lock ordering escape hatch

Use `Locked::adopt` and friends to not have to create
`Locked::new_locked` at specified lock levels.

This should make lock ordering evolution less brittle since we don't
have to repeat the lock level anywhere anymore.

Had to amend how `adopt` works because it had been implemented in a
vacuum before. Now we finally see it working.

Only the crate-local `Locked` type should be used since there's no need
to create one-off `lock_order::Locked` instances anymore.

Original-Fixed: b/42077415
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/966908
Original-Revision: 95201fa8fa6cab7f1cf618396c28a97180e6d7c9
GitOrigin-RevId: 3b258b7d6a62531753cf86eda0c7c043a848c957
Change-Id: I12826e0a75a86e220d86fd1ef137202f757d7a4a
1 file changed
tree: 23e9b3dc365ee14b1d55ba721544bf7ae054d26a
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.