3.0.0-rc2
core: prevent crash in tee_mmu_final() on TA loading error

If the creation of the TA execution context fails before the mapping
directives are initialized, tee_mmu_final() will be called with the TA
context field mmu being NULL.

This change allows tee_mmu_final() to be called with uninitialized
mapping resources without crashing the core.

Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org>
1 file changed
tree: 6d71a1610e9d84100bcd7b0d7702673c8575b39e
  1. .github/
  2. core/
  3. documentation/
  4. keys/
  5. lib/
  6. mk/
  7. scripts/
  8. ta/
  9. .gitignore
  10. .shippable.yml
  11. .travis.yml
  12. CHANGELOG.md
  13. LICENSE
  14. MAINTAINERS.md
  15. Makefile
  16. Notice.md
  17. README.md
  18. typedefs.checkpatch
README.md

OP-TEE Trusted OS

Contents

  1. Introduction
  2. License
  3. Platforms supported
  4. Get and build OP-TEE software
  5. Coding standards 5. checkpatch

1. Introduction

The optee_os git, contains the source code for the TEE in Linux using the ARMĀ® TrustZoneĀ® technology. This component meets the GlobalPlatform TEE System Architecture specification. It also provides the TEE Internal core API v1.1 as defined by the GlobalPlatform TEE Standard for the development of Trusted Applications. For a general overview of OP-TEE and to find out how to contribute, please see the Notice.md file.

The Trusted OS is accessible from the Rich OS (Linux) using the GlobalPlatform TEE Client API Specification v1.0, which also is used to trigger secure execution of applications within the TEE.


2. License

The software is distributed mostly under the BSD 2-Clause open source license, apart from some files in the optee_os/lib/libutils directory which are distributed under the BSD 3-Clause or public domain licenses.


3. Platforms supported

Several platforms are supported. In order to manage slight differences between platforms, a PLATFORM_FLAVOR flag has been introduced. The PLATFORM and PLATFORM_FLAVOR flags define the whole configuration for a chip the where the Trusted OS runs. Note that there is also a composite form which makes it possible to append PLATFORM_FLAVOR directly, by adding a dash in-between the names. The composite form is shown below for the different boards. For more specific details about build flags etc, please read the file build_system.md. Some platforms have different sub-maintainers, please refer to the file MAINTAINERS.md for contact details for various platforms.

The Maintained column shows:

  • A green image if the platform is actively maintained: either tested successfully with the latest release (N), or is a newly supported platform.
  • An orange image if the platform was last tested successfully with release N-1.
  • A red image if the last successful test report is older.
PlatformComposite PLATFORM flagPublicly available?Maintained?
ARM Juno BoardPLATFORM=vexpress-junoYesActively Maintained
Atmel ATSAMA5D2-XULT BoardPLATFORM=samYesActively Maintained
FSL ls1021aPLATFORM=ls-ls1021atwrYesActively maintained
NXP ls1043ardbPLATFORM=ls-ls1043ardbYesActively Maintained
NXP ls1046ardbPLATFORM=ls-ls1046ardbYesActively Maintained
FSL i.MX6 Quad SABRE Lite BoardPLATFORM=imx-mx6qsabreliteYesNot maintained v2.2.0
FSL i.MX6 Quad SABRE SD BoardPLATFORM=imx-mx6qsabresdYesNot maintained v2.2.0
FSL i.MX6 UltraLite EVK BoardPLATFORM=imx-mx6ulevkYesActively Maintained
NXP i.MX7Dual SabreSD BoardPLATFORM=imx-mx7dsabresdYesActively Maintained
ARM Foundation FVPPLATFORM=vexpress-fvpYesActively Maintained
HiSilicon D02PLATFORM=d02NoActively Maintained
HiKey Board (HiSilicon Kirin 620)PLATFORM=hikey or PLATFORM=hikey-hikeyYesActively Maintained
HiKey960 Board (HiSilicon Kirin 960)PLATFORM=hikey-hikey960YesActively Maintained
Marvell ARMADA 7K FamilyPLATFORM=marvell-armada7k8kYesActively Maintained
Marvell ARMADA 8K FamilyPLATFORM=marvell-armada7k8kYesActively Maintained
Marvell ARMADA 3700 FamilyPLATFORM=marvell-armada3700YesActively Maintained
MediaTek MT8173 EVB BoardPLATFORM=mediatek-mt8173NoActively Maintained
Poplar Board (HiSilicon Hi3798C V200)PLATFORM=poplarYesActively Maintained
QEMUPLATFORM=vexpress-qemu_virtYesActively Maintained
QEMUv8PLATFORM=vexpress-qemu_armv8aYesActively Maintained
Raspberry Pi 3PLATFORM=rpi3YesActively maintained
Renesas RCARPLATFORM=rcarNoActively maintained
Rockchip RK322XPLATFORM=rockchip-rk322xNoActively maintained
STMicroelectronics b2260 - h410 (96boards fmt)PLATFORM=stm-b2260NoActively maintained
STMicroelectronics b2120 - h310 / h410PLATFORM=stm-cannesNoActively maintained
Texas Instruments DRA7xxPLATFORM=ti-dra7xxYesActively maintained
Texas Instruments AM57xxPLATFORM=ti-am57xxYesActively maintained
Texas Instruments AM43xxPLATFORM=ti-am43xxYesActively maintained
Xilinx Zynq 7000 ZC702PLATFORM=zynq7k-zc702YesNot maintained v2.3.0
Xilinx Zynq UltraScale+ MPSOCPLATFORM=zynqmp-zcu102YesNot maintained v2.4.0
Spreadtrum SC9860PLATFORM=sprd-sc9860NoNot maintained v2.1.0

4. Get and build OP-TEE software

Please see build for instructions how to run OP-TEE on various devices.


5. Coding standards

In this project we are trying to adhere to the same coding convention as used in the Linux kernel (see CodingStyle). We achieve this by running checkpatch from Linux kernel. However there are a few exceptions that we had to make since the code also follows GlobalPlatform standards. The exceptions are as follows:

  • CamelCase for GlobalPlatform types are allowed.
  • And we also exclude checking third party code that we might use in this project, such as LibTomCrypt, MPA, newlib (not in this particular git, but those are also part of the complete TEE solution). The reason for excluding and not fixing third party code is because we would probably deviate too much from upstream and therefore it would be hard to rebase against those projects later on (and we don't expect that it is easy to convince other software projects to change coding style).

5.1 checkpatch

Since checkpatch is licensed under the terms of GNU GPL License Version 2, we cannot include this script directly into this project. Please use checkpatch directly from the Linux kernel git in combination with the local checkpatch script.