| commit | 4feef4a3ae4e2d34371f0cc17b5df22a201eb05c | [log] [tgz] |
|---|---|---|
| author | Kevin Lindkvist <lindkvist@fuchsia.infra.roller.google.com> | Mon Apr 28 08:12:07 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 28 08:13:41 2025 -0700 |
| tree | 760536a3c07bd884650e2434d1042abb5d130e15 | |
| parent | 24b1f0719d3c989c75c1054860ad7f316730b811 [diff] |
[roll] Roll fuchsia [starnix][ext4] Move pager out of starnix kernel When suspending a Starnix container all the threads in the container are paused. If the pager threads are suspended before the pager client's the suspend operation may deadlock. This is because the client threads can end up blocked in Zircon (on the pager response), which prevents them from being suspended. This change moves the pager threads into the starnix_runner component, which is the same component that is responsible for suspending the container threads. This guarantees that the pager requests can always be handled. Original-Fixed: 410933064 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1260704 Original-Revision: 1de8b923df5284ec1007a07862fba86224280cba GitOrigin-RevId: d35779c922a5d703d32723fc5d4c05390f968478 Change-Id: I57077d6b2f95d376347b1c532789f8a156f21503
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 in one of the communication channels documented at get involved.
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.