[roll] Roll fuchsia [starnix] Perform container component-run work as kernel-internal

Temporarily mark the calling system-task as performing a kernel-
internal operation during setup of a new component in a container,
to prevent LSM checks (e.g. against SELinux policy) from blocking
them.

The component itself will receive a new task security state with
the appropriate labeling information, regardless of the creating
system-task being marked as internal.

Original-Bug: 417380368
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1435436
Original-Revision: ae1762ab0184526590c8eb33d401e3610cac6dc4
GitOrigin-RevId: 09387d5a3a199eb8612d77e08f32d32be9cc52ee
Change-Id: I2c29135b195c0d131448900e117d1855086bd939
1 file changed
tree: b916c6d023603cb3bc5699b42443044e1db7823d
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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.