[roll] Roll fuchsia [kernel][vm] Avoid updating nested child limits

Fixes a bug in the Resize logic that could cause it update the
parent_limit_ of nodes that were not its direct children. Aside from
any other user visible data correctness issues this might cause this
can also result in child VMOs failing to clear out content from their
hidden parent, since they do not think they see it, trigger a kernel
assertion failure.

This commit fixes the problem by serializing clone creation with
resizing, and adds a regression test.

Original-Bug: 415665459
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1271667
Original-Revision: 5a46738732f01f74b4d83fc9bea34e9961f66526
GitOrigin-RevId: 4901edee901ed559c634220434db25577166a303
Change-Id: Id8a5bd2b34fb124a43040ae761e68132db138cfc
1 file changed
tree: 7e8d2eae0ae9e5b6cbc8899de51a3c772c84f024
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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 in one of the communication channels documented at get involved.

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.