commit | 422991c6a7b3c1d555a7b862e80609124354b55c | [log] [tgz] |
---|---|---|
author | Nick Maniscalco <maniscalco@google.com> | Tue Jan 29 11:04:00 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 29 23:51:52 2019 +0000 |
tree | bcae373ec5206c41cf10310f7e75672f41193ae4 | |
parent | d23797ce7ed994cc79fcf85734e53c10905d04be [diff] |
[object][job] Fix bug where process creation bypasses ZX_POL_NEW_ANY This change fixes a bug where process creation would succeed even when the job policy prohibited it via ZX_POL_NEW_ANY. See ZX-3364 for details. Add test and static_asserts to reduce the likelihood of regression. Bug: ZX-3364 #done Test: "k ut job_policy" Change-Id: Ifcb22d3c341d1ebc1c8e37c264e5833305dacf59
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.