[roll] Roll fuchsia [kernel] Trigger OOM action on handle allocation failure

If we fail to allocate a handle, the system is likely hosed so trigger
an OOM action.  See https://fxbug.dev//379936010#comment8 for
motivation.

In the future we should move the allocation failure reporting
mechanism off of the PMM to a more general place.  Perhaps
MemoryWatchdog.

Original-Bug: 42175304
Original-Fixed: 379936010
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1164072
Original-Revision: 88c98813488e47824810e81d1e914cff36fbd70e
GitOrigin-RevId: 70f575d28958e0618b4981a7159fc8a50dddbcee
Change-Id: I55aec15e3f02c34a51bc858a6c3154bab9715f7e
1 file changed
tree: 2d0ed55a8015b406de403125ec6d5be0cfa5abdf
  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 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.