| commit | 36ed6b54d05495aa5ea94cef7e34dd6695b21e85 | [log] [tgz] |
|---|---|---|
| author | Nick Maniscalco <maniscalco@fuchsia.infra.roller.google.com> | Wed Jan 31 00:34:05 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 30 16:35:43 2024 -0800 |
| tree | 1c3d80045b08492ced97f3e56fb2623bb78f5578 | |
| parent | 62bb0609551a01d7f09671163e358de025989b53 [diff] |
[roll] Roll fuchsia [kernel][oom] Trigger OOM response on "terminal" heap alloc failure A while back, we implemented https://fuchsia-review.googlesource.com/c/fuchsia/+/645109 to ensure we trigger a system OOM response (when so configured) when an allocation failure occurs. We wired it up to pmm_alloc_page(s). However, we did not wire it up to pmm_alloc_contiguous, since a failure there is not necessarily OOM-worthy. This change updates cmpct_malloc to trigger a system OOM if it fails to allocate because it was unable to obtain a large enough block via pmm_alloc_contiguous. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/983085 Original-Revision: 155b6170f81bdcca6e9c971f67e67e5639ab9f5b GitOrigin-RevId: c7fb77930e5a4f20ab26d07c3c6240990e1ebbe9 Change-Id: Ib8417ef8959069ef049ecc46b6a9cb336c235bfb
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.