commit | 54502af03b0587db6bb01bf6cc935888edd5cb82 | [log] [tgz] |
---|---|---|
author | Sean Klein <smklein@google.com> | Tue Mar 20 10:40:52 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Mar 21 00:52:24 2018 +0000 |
tree | a18e054f226b35a32238da69070f3918880dabe0 | |
parent | 9c0e32197bf6fb4e63624d0f09970b20faa3bd1a [diff] |
[fs] Ensure Vnode::Close is called on unclean teardown The contract of ulib/fs is that every call to "Open" will be paired with an accompanying call to "Close", in the event of either: 1) A client sends a close message explicitly, making their channel defunct (and no longer observed), or 2) A client closes their channel, implicitly closing their connection to the filesystem. Although the Connection class in ulib/fs would properly cancel waits and tear down the connection object, it previoulsy missed sending a close in the second condition, since it invoked "CallHandler" while the channel was not yet ZX_HANDLE_INVALID. This patch ensures that the close handler is invoked in this condition. ZX-1853 #done Change-Id: I291192cae32e8250f7cef932cbf1a4de4b8b2d2d
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
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/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.