[roll] Roll fuchsia [kernel][mmu] Handle failed initialization Aspace initialization can fail if the top level page table could not be allocated due to OOM. In this scenario AssertEmptyLocked would otherwise blindly dereference the top level page table and fault. Given the DisableUPdates is a temporary code path for debugging, performing this check here is considered preferable to shuffling the VmAspace code paths to avoid calling DisableUpdates on a failed init. Original-Bug: 124009 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/822987 Original-Revision: aae8ea53335c3b23585dcc8078bed5f06a36605f GitOrigin-RevId: e89870f8f6aa334446592d1d471089965c891468 Change-Id: I3e06c640ea3296fde1a85c88374fbaf2e7a89890
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.