Age | Commit message (Collapse) | Author |
|
because once the Android.bp finder is enabled, it will be found anyway,
and this will allow us to confirm separately that adding this Android.bp
is successful.
Bug: 64363847
Test: m -j
Test: ./out/host/linux-x86/nativetest/libnvram-core-tests/libnvram-core-tests
Test: ./out/host/linux-x86/nativetest64/libnvram-core-tests/libnvram-core-tests
Change-Id: I8c23eacf3512ea0ad4a06553ca19506bfc5c40e6
|
|
See build/soong/README.md for more information.
Test: mmma sytem/nvram
Test: out/host/linux-x86/nativetest{,64}/libnvram-core-tests/libnvram-core-tests
Change-Id: I3fb44a38a56bc5180eda8f98bf327a98b3030540
|
|
Test: links
Change-Id: I8dfa201c20fb0081a00de779449d5f9acf29c32d
|
|
This change fixes a few typos and clang tidy warnings related to the
"llvm-namespace-comment" checks.
Bug: 26936282
Test: WITH_TIDY=1 WITH_TIDY_CHECKS="llvm-namespace-comment" mm
Change-Id: Ib2783ee52713c2b0e5da1b8131c7baec696e74f9
|
|
Bug: http://b/32019064
Test: builds
Change-Id: I855a44786617faaf5c6e0e48644bc992b31fb2b3
|
|
There's no need to use a different name for target and host moudles. In
Soong, it's better to use the same for both, as target and host modules
can be defined at the same time.
Change-Id: Icc70c3918f53dc7bba07d5219c6c1468da83328f
|
|
This makes sure any storage status codes coming from the persistence
layer are within the known range. Any status code outside the range
are mapped to kStorageError. This adds an extra safety net that
catches misbehaving storage implementations or problems with linking
stale NVRAM object code after adding status code definitions at run
time.
Change-Id: Ia6418b6a8d56ac2a812434fe2565aef63a82b59a
|
|
This adds commands that allow clearing the entire NVRAM contents. This
can be used by firmware to implement the correct behavior as part of
device recovery. There's always the risk of malicious invocation of
the reset logic, so the new code is behind a compile flag which isn't
enabled by default.
BUG: 29260086
Change-Id: I8eb8a4953ed62ff75b8242daa60c1e4f99bf254d
|
|
This moves the details of interfacing with crypto libraries behind a
clean interface, so crypto can be swapped out as needed. Now that
swapping out crypto libraries is easy, use BoringSSL for the main
Android build. We can now always replace it with something else if
that's need in other environments.
BUG: 29238681
Change-Id: I9af046b62273ede4c98d4239a4774c25764dbdaf
|
|
Bug: http://b/27287913
Change-Id: Ib4b60dba211c054eb551a2bbf8b4ff2ba6f12d8a
|
|
This adds some bare-bones stubs to replace gtest in order to run the
NVRAM core tests also within a trusty image.
BUG: 27194661
Change-Id: If88e9903e19253bb93a10cb850511bfca5189da7
|
|
This method, added in v1.1 of the HAL, allows an implementation to
report the maximum supported size for a single space.
This CL also includes a few enhancements to improve testing and adds a
top level Android.mk for convenience.
BUG=27480753
Change-Id: I962cc7a31e869e72920cd80146b69974e50d5745
|
|
This sets LOCAL_CLANG := true for all nvram targets. While at it,
consisitfy the order of statements across the different files.
Change-Id: Iaf1200a5ae3407c600a6f09692d2c87e833244f3
|
|
The code should use PRI... macros from inttypes.h when formatting
fixed-with integer types. This prevents compiler warnings due to
mismatches between actual type size and the compiler-target dependent
standard format constants.
Change-Id: I6e810187da0e6a136fc104c095bcffa95116bbb1
|
|
Add unit tests for the remaining NvramManager operations. This
actually uncovered buggy behavior in edge cases when operations run
into errors but don't leave the system in predictable internal state.
This change fixes these issues as well, so the tests pass.
BUG: 26978195
Change-Id: If17c6a2073bdcea9f804385aa2fa5050e2f2c8d0
|
|
Implement NV_CONTROL_WRITE_EXTEND, i.e. access-controlled NVRAM spaces
that are hash-extended on write. This can be used for anything that
employs hash-chaining, e.g. for audit logging.
BUG: 26973380
Change-Id: Icb03134aa55efb52250477056ce877b3d046bc0c
|
|
This adds a first batch of test cases for the Trusty NVRAM HAL
implementation, covering initialization and space creation.
BUG: 26978195
Change-Id: I0c626d3131e7b75d76c004b455799c59040e9c9e
|
|
This adds the logic for NVRAM HAL operations that manipulate
individual spaces, i.e. reading, writing and locking them.
BUG: 25762540
Change-Id: Idb3a1c5c796fde32ef77d1a68c4cc554150acb8c
|
|
This implements the first batch of NVRAM operations: GetInfo,
CreateSpace, GetSpaceInfo and DisableCreate. Operations to manipulate
individual spaces will follow in a subsequent CL.
BUG: 25762540
Change-Id: I74c6bcf7804cecbe7630479fbdd6bb0a0a668c7b
|
|
This adds TrustyNvram, which will hold the main logic implementing the
semantics mandated by the access-controlled NVRAM HAL spec.
BUG: 25762540
Change-Id: I40914bd161ca58b4f79d32a1b82c6754db5cfca8
|
|
This lays down the basic interfaces for reading and writing persistent
storage objects used by the NVRAM implementation. We'll have two
different types of objects: The header contains global bookkeeping
information as well as list of spaces that are currently defined. For
each space, there's a space-specific storage object that holds space
metadata and contents.
BUG: 25762540
Change-Id: Iadce20f76d84b3ed1ea25762ec673daae31d6b1d
|