commit | 43e989700ccb9d8c1a3cf8aa2ebbf67773786e27 | [log] [tgz] |
---|---|---|
author | Mark Seaborn <mseaborn@google.com> | Wed Jan 23 14:38:00 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 30 01:23:59 2019 +0000 |
tree | e198c98f15a47453cddb21557f84cc1f59dc56f9 | |
parent | f3bfcb603e6e481658aced768f5b1e3dbbd550f0 [diff] |
[ulib][inspector] Make "bad handle" job policy exceptions fatal This code path applies to: * Drivers, because they have ZX_POL_ACTION_EXCEPTION set for ZX_POL_BAD_HANDLE by devmgr. * Standalone Zircon only. In Garnet and Topaz, Crashpad gets used for crash handling instead, and that already turns "bad handle" job policy exceptions into fatal errors. This change therefore brings standalone Zircon's behaviour into line with the behaviour when running a full Fuchsia system. Test: I added "printf(...); zx_handle_close(1); printf(...)" into TestDriverBind() in zircon/system/dev/misc/test/test.cpp. * On standalone Zircon, before this CL, the close call gives a warning only (the "after" printf() runs); after, the close call is fatal. * On Garnet and Topaz, the close call is fatal before and after this CL (only the "before" printf() executes). Bug: ZX-922 Change-Id: I265730c8e2f203f551b146b6d38b6a98dae0bb0c
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.