[roll] Roll fuchsia [starnix] Add a KernelSignal for cgroup freezer

Regular signal mechanism should be unchanged. The new signal will be
stored in another queue to ensure internal signals will never be
ignored or masked. Higher priority ensures that no user signals
jump the queue, e.g. ptrace, that will delay the delivery. This design
is about implementation convenience than about observable behavior.

Cgroup freezer uses the signal handling to ensure the thread exists
the restricted mode and stays in a "safe point", where we know the
thread is not holding any critical Starnix resources, for example
internal mutex locks

Original-Bug: b/333766695
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1161597
Original-Revision: eaed6c586a07f719f40ba2bb6da81be31953e4d6
GitOrigin-RevId: 793a384f71b554f8824e3e7aec6e103dcbdfd5ef
Change-Id: Id08963eefb07860f7cb14d00348ff236dddfe1f7
1 file changed
tree: efa78ca3293c1b1ff8e5d3ee158456214a493bcb
  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.