commit | 919d39782db28c46b3ef578b504936daccbdba5c | [log] [tgz] |
---|---|---|
author | Todd Eisenberger <teisenbe@google.com> | Mon Mar 19 17:42:15 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Mar 20 17:41:39 2018 +0000 |
tree | c13a9ff565bded0ba18606f7a12710fa33f7dfb7 | |
parent | cb89c092f5596b76f560e7416420e9f6fc09f9c0 [diff] |
[dev][sdmmc] Fix missized buffer and missing returns Fix two problems: 1) The sdmmc_query function was reporting the wrong struct size, causing transaction structs to be incorrectly sized. With a small change to the struct, this could easily turn into a buffer overrun when accessing the transaction structure. 2) Two early-return cases were missing returns, potentially causing two completion callback invocations in those cases. ZX-1851 #done Change-Id: I35c0cbd46f223f648799e65da5801775210cb6fc
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.