[roll] Roll fuchsia [sestarnix] Update init_child_process security state

Previously tasks that were injected as children of init were using the
kernel's security context. This was causing tests to fail a bunch of
security checks. In production tasks are not created this way.

Now, we instead create the security context with `task_alloc` on the
init task.

A future change will allow test components to specify this more
directly.

Original-Bug: 355809979
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1097576
Original-Revision: 25edc5af8cd38bf4482639731b101077e3395c4f
GitOrigin-RevId: df616b81b3f938c6c9488cbde05a56e9974a28c6
Change-Id: I257965e5c174d8511b4a370ef75ebebd5f08c1a7
1 file changed
tree: 175543863933aaffc6b1a3c405793fafd6b0eaef
  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 via the IRC channel #fuchsia on Freenode.

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.