[roll] Roll fuchsia [kernel][vm] Improve CSM lock annotations

Changes the ContentSizeManager::Operation to have a constant parent_
references and use a separate valid_ flag for tracking validity. This
allows for the external users of the operation to used AliasedLock
acquisitions instead of having to assert that the lock is held.

Asserting that the lock is held is still needed for when the CSM itself
is iterating over the operation queues.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1103752
Original-Revision: 4315f1fa9857c331a64e4a51e930425726bc6b88
GitOrigin-RevId: 787c1395d1e1e3d81990bc2ab2752e0758beac3a
Change-Id: I0b6b1e98d12015261d154cc34770a248d9cf4126
1 file changed
tree: 37a58679bd3c863eaa20b5b751fec215859b985f
  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 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.