This avoids the extra DT_NEEDED entry even in cases where libc++.so
isn't needed. This is also consistent with Clang driver implementation
which uses --as-needed around libc++.so.

Bug: ZX-4099
Change-Id: I76475896b7ea2c825a97f28b7b09e53228b468c6

We can't assume that there will always be a block device. For now, we
can assume that there will always be a platform-bus driver bound.

It would be better if we created a fake devfs for these tests but since
device discovery is going to signficantly change in the near future this
should be good enough for now.

ZX-4090 #done

Change-Id: I668e6a13ec273f83d13654ba692ea92763fc41b8

This change implements a very simple command line tool/uapp application to consume the
disk objects for minfs and recursively iterate over all of them.
Please note that this is not interactive at the time being, but is implemented
as a first implementation of the disk-inspector tool. It is a good way to
test the different apis of the disk-inpector library.

Testing: The application itself is pretty dumb and doesn't need unit tests.
          The unit tests for minfs backend are already added as part of the change:
          https://fuchsia-review.googlesource.com/c/fuchsia/+/277175
Change-Id: Icd211c30bdb2c82c9f242447d8fddc5d7620c323

Test: CQ

Change-Id: I0b8a33851af712c41c0bcf84d05a150a29e99730

Change-Id: I0a6b422086d82e61c3761d9abc3a0b2e147da3df

ZX-3736

Test: stack-test
Change-Id: Ib7a55021bf5790352a451a34a5cad1e74fda780b

This updates the ISP test fidl interface to comply with abarth's
fidl rules.

TEST: No functionality change.
Change-Id: I6660a9bf47e66ba7337c95245f9e7ade5f9dfb3d

Step #1's local testing was misconfigured and failed to test the
step #2 integration build properly as the bots do, so a trivial
bug slipped through.

Bug: ZX-3365
Change-Id: I331b3b989125c5982632d310daa8b7d512a49faf

We use the __TA_xxx macros to annotate code for clang's thread safety
analysis features.  The thread safety analysis feature works by
comparing the annotations on types with the annotations on code using
those types and generating a warning if the code is identified that is
inconsistent with the annotations or the defined semantics of the
annotations.  We frequently use these annotations to describe the
relationship between code and types from the C++ standard library, such
as std::mutex.  These types are annotated in the libc++ standard library
implementation if the preprocessor define
_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS is set.

In the Fuchsia build, we always set -Wthread-safety and -D_LIBCPP_...
compiler flags together so the annotations are consistent internally.
Some SDK customers use the fuchsia SDK and -Wthread-safety flag without
setting the preprocessor define as they use other libraries which use
the C++ standard library types in ways incompatible with thread safety
analysis.  This causes issues when compiling code that uses the
__TA_xxx macros with types like std::mutex.

This updates the __TA_xxx macros to only enable annotations if we can
tell that C++ standard library types are annotated (using the
_LIBCPP_... macro) or if we're in kernel code that we always control.

This also updates zircon/kernel code to use the non-public macros
defined in zircon/system/private so that they are enabled even when
libc++ is not involved.

ZX-4091 #done

Change-Id: I74910f6963d79bd2a53cf5d89a183252c5b58e7e

The double free would occur if
1) some thread invoked Cancel() to queue destruction of a ProxyIostate,
   and
2) before that packet was processed, the ProxyIostate's handler ran and
   decided to destroy itself.

Bug: ZX-4060
Change-Id: I3b9c7275c4e0cd2dc3a6c6cd2d2376c947eb627a

This moves the ProxyIostate and ConnectionDestroyer types into their
own files, and feeds them async dispatchers via injection rather than
environmental globals.

Change-Id: Ifeadbed02e92a7e2a7af5346ddd253af74112abf

Bug: ZX-4099 #done
Change-Id: I23e6d4b163ddc8616a22decc2029424888305cdf

In order to make the code more encapsulated , this change removes the "friend"
relation between fsck and minfs class as well as inode-manager class. We use the interfaces
added as part of inspector changes and instead of fsck directly accessing the private members,
we use these Interfaces instead.

Testing: No behavior change. Merely converted private members to be accessed via public interfaces instead of directly via friend relation.
Change-Id: I8fae7acf6d59b47ad2c3376a91d602a127e34de7

Bug: DX-538

Testing:
* sdk archive builds correctly.
* workspace generated properly
* tests pass as long as I use the same version of bazel that infra uses (0.17.2)

Change-Id: I808d1e6ca9d66b56ba6ad8f2e3a06270fd49c79d

The libc++ support changes refactored the GN magic around the vDSO
($zx/system/ulib/zircon) target and broke the semantics for derived
environments of the user environment, i.e. user.fuzzer.  Fix that.

Bug: BLD-430 #comment Fix GN build regression introduced by libc++ support.
Bug: ZX-1751 #comment Fix GN build regression introduced by libc++ support.
Change-Id: I47bd7683e97aedb7b2ab7c8ab05a136cd936ff26

Change-Id: I960886bae1a318c96153c0ce69b90d0a55c6ee38

Change-Id: I8cd0ba4f4ae1af47271462a6da8ddcd7813a19d8

This restores most of the incidental improvements in the original commit
396d2162, while keeping logging silent.

This reverts commit 7f7e4ffb.

Change-Id: Ie8183448c8cddb03f0423287d67183b0a3658cf6

Test: CQ

Change-Id: Iec3c3e3c83bab280fc73ca4c5d2e87305d1a1666

Change-Id: I9df939c00866878c97a6ae2e0cfc4bc36b8811c0

Change-Id: I3c15087e0535df819ce1d281766dd58f11cdd69a

Change-Id: Ia3851cab38e65b8d7be572aba9c5b89dc92c8167

Change-Id: Ia4ebd88e8ad9b9f73937e94c107aa211a21859e4

Change-Id: I58d1754ca577703e082a3b094373b150eb54d263

Change-Id: I24fcabc7c34e1204c42da5d1b39af19f5da5bb09

Change-Id: I141bb03798bf20a1308dc0d9fe708d498ea8e7c0

Change-Id: I0f9b5d25d3ac30cdf9ea980dfa73b7dbac2bef03

Change-Id: I662592845b752ae2dffaf969446946840bfa259e

Change-Id: Ia0cd86655e53e89ce7511a91d3357c041f890c6d

Change-Id: I4d26f0c5253cd7b7b52b46358936d9a37b9a0031

Change-Id: Iec0b5b83dbcabb41d64f6c13682ac8bb3ddf68e3

Change-Id: I8eb0d866deadd3f0ff0631f334b309fbe52e14dd

Change-Id: I3f320db87460ca6eb7535d46243077562d1a6b5f

Change-Id: I1b16d937dfc1b6f735f12048e76e6691ca325ecb

Test: CQ

Change-Id: I2af3d92b069aef6be422eba040823c4b88acd548

This allows processes further down the job-hierarchy to be able to get
access to the RootJob. This is useful for processes such as the
devcoordinator (once component_manager is in place) and utilities like
ps.

Eventually, we will want to further limit or entirely get rid of this
interface. That will happen once component_manager is in place.

ZX-4002
ZX-4072

Change-Id: I4b1e75a7841a04ea2cc7da374e42257d4802e619

Test: CQ

Change-Id: I6ae5d995f2e9c824b82aff9c9c985d604e7a6cbf

Test functions are now ordered alphabetically, just like the calling
sequence at the bottom of lint_finding_tests.cpp.

Test: fidl-compiler-test
Change-Id: Ic0c60a83ad530f8cf3caf3d50c83c1649e4f4861

All "case" checks are complete.

Test: fidl-compiler-test
Change-Id: Ie773e757177e82a76e30e1bfafaf1de97010e49b

This is part of a soft transition to replace fuchsia-foo-bar names
with fuchsia.foo.bar names for the directory and GN target names for
FIDL libraries defined in //zircon/system/fidl and accessed in legacy
GN via //zircon/public/fidl.  After the transition, the directory and
GN target names will exactly match the FIDL library names everywhere.
 1. Make //zircon/public/fidl/a.b.c alias //zircon/public/fidl/a-b-c
 2. Convert all //zircon/public/fidl uses outside fuchsia.git & integrate
 3. Convert all //zircon/public/fidl uses inside fuchsia.git
 4. Remove transition hacks
 5. Enforce naming conventions in GN templates
This is step 1.

Bug: ZX-3365 #comment Start soft transition for //zircon/public/fidl
Change-Id: Iabbbee27a2a442bf80da88efb9bd9ddeb729215b