Tock 2.2

Tock 2.2 represents two years of Tock development since v2.1.1. This release contains almost 3900 commits made across 840 PRs by 90 contributors (of which 48 are new contributors!). It is the first Tock release that can compile on a stable Rust toolchain, and contains many other important fixes, new subsystems, new platforms, new drivers, and major refactors.

Backwards Compatibility

Tock 2.2 extends its system call interface through one new system call (Yield-WaitFor), but retains backwards compatibility with Tock 2.1.1 for its core system call interface and all stabilized drivers.

In this release, we revised Tock's alarm system call driver implementation to predictably wrap its ticks values at (2**32 - 1) ticks, across all platforms. Before this change, hardware alarm implementations that were less than 32 bit wide would wrap before reaching (2**32 - 1) ticks, which complicated correct alarm handling in userspace. In Tock 2.2, these alarm implementations are scaled to 32 bit, while also scaling their advertised frequency appropriately. While this change is non-breaking and compatible with the previous alarm implementation, it can expose such scaled alarms to userspace at significantly higher advertised frequency values. Userspace alarm implementations that did not correctly handle such high frequencies may need to be fixed to support this new driver implementation.

Security and arch-crate Fixes

Tock 2.2 includes important and security-relevant fixes for its Cortex-M and RISC-V architecture support.

• When switching between applications, the RISC-V PMP implementation did not correctly invalidate any additional memory protection regions that are not overwritten by the target app's PMP configuration. Under certain conditions this can allow an application to access private memory regions belonging to a different applications (such as when using IPC).

• The Cortex-M (Armv7-M) and Cortex-M0/M0+ (Armv6-M) hard fault, interrupt and svc handlers contained a bug that could allow an application to execute in privileged mode after returning from the handler. This allows an application to execute code at kernel privileges and read / write arbitrary memory.

Stable Rust Support

This release removes all nightly Rust features from all of Tock's core kernel crates (such as kernel, arch/*, and chips/*). This allows Tock to be built on the Rust stable toolchain for the first time!

We demonstrate this by switching the hail board to a stable toolchain in this release. We continue to compile other boards on the Rust nightly toolchain, as this enables some important code-size optimizations (such as by compiling our own, size-optimized core library).

AppID, Credentials and Storage Permissions

This Tock release revisits how applications are identified in the kernel, and introduces a set of mechanisms that allow developers to identify, verify, and restrict applications that are running on a Tock kernel. AppIDs are the core mechanism to enable this and identify an application contained in a userspace binary. AppIDs allow the kernel to apply security policies to applications as their code evolves and their binaries change. We specify AppIDs, Credentials and their interactions with process loading in a draft TRD.

Additionally, we introduce a mechanism to assign applications permissions to access some persistent storage (e.g., keys in a key value store). This mechanism interacts with AppIDs (ShortIDs) and is also specified in a a draft TRD.

Major Refactors and Interface Changes

We implement a number of kernel-internal refactors and interface changes:

• System call drivers are now mandated to either return Success or Failure(ErrorCode::NODEVICE) for a command system call with command number 0. Previously, some drivers used this command number to also convey additional information to userspace. This release does not change the interface of any stabilized drivers, which will be updated as part of Tock 3.0.

  Relevant PRs:

  • Syscall Spec: Allow Command 0 to return Success with value or lock it down by @ppannuto in https://github.com/tock/tock/pull/3626
  • Update command 0 comments on stabilized userspace drivers by @hudson-ayers in https://github.com/tock/tock/pull/3402
  • capsules: ensure driver existence check by @Samir-Rashid in https://github.com/tock/tock/pull/3613

• Tock 2.2 introduces [a new policy to support external dependencies][external-deps] in the upstream Tock codebase. As part of this effort, we split up the existing, single capsules crate into multipe crates (such as capsules-core, capsules-extra, and capsules-system) with different guarantees concerning stability and use of external dependencies. The core capsules crate contains capsules deemed essential to most Tock systems, as well as virtualizers which enable a given single peripheral to be used by multiple clients. Other capsules have been moved to the extra capsules crate. The system capsules crate contains components that extend the functionality of the Tock core kernel, while not requiring unsafe.

  Relevant PRs:

  • doc: Add ExternalDependencies.md by @alistair23 in https://github.com/tock/tock/pull/3312
  • capsules: split into core/ and extra/ (implementing #3346) by @lschuermann in https://github.com/tock/tock/pull/3396
  • Create system capsules crate, move kernel implementations, update boards by @bradjc in https://github.com/tock/tock/pull/3992

• Furthermore, the DeferredCall and DynamicDeferredCall subsystems have been replaced with a more lightweight and unified deferred call infrastructure. This new approach has a smaller code size overhead and requires less setup boilerplate code than .

New Boards

This release features support for 7 new boards in the upstream Tock codebase:

• sma_q3 by @dcz-self in https://github.com/tock/tock/pull/3182
• particle_boron by @twilfredo in https://github.com/tock/tock/pull/3196
• BBC HiFive Inventor by @mateibarbu19 in https://github.com/tock/tock/pull/3225
• SparkFun LoRa Thing Plus by @alistair23 in https://github.com/tock/tock/pull/3273
• makepython-nrf52840 by @bradjc in https://github.com/tock/tock/pull/3817
• Nano33BLE Sense Rev2 by @TheButterMineCutter in https://github.com/tock/tock/pull/3717
• VeeR EL2 simulation target by @wsipak in https://github.com/tock/tock/pull/4118

New HILs, Drivers and Features

Tock 2.2 features 6 new HILs:

• CAN bus by @teonaseverin in https://github.com/tock/tock/pull/3301
• Buzzer by @TeodoraMiu in https://github.com/tock/tock/pull/3084
• DateTime by @Remus7 in https://github.com/tock/tock/pull/3559
• CycleCounter by @codingHahn and @hudson-ayers in https://github.com/tock/tock/pull/3934
• public_key_crypto/SignatureVerify by @bradjc in https://github.com/tock/tock/pull/3878
• Servo by @inesmaria08 in https://github.com/tock/tock/pull/4126

IEEE 802.15.4 and 6LoWPAN Stack

We can now join a Thread network by running OpenThread as a libtock-c userspace implementation, thanks to a major refactor and redesign of Tock's IEEE 802.15.4 and 6LoWPAN stack.

Known issue: UDP transmit functionality is currently broken with a bug / inconsistency between the kernel and libtock-c implementation. When executing the transmit syscall, the libtock-c application fails to provide the src address and fails the error check that occurs for the transmit syscall. For more information, see the Tock 2.2 release testing issue: https://github.com/tock/tock/issues/4272#issuecomment-2569993915

Fixes, Improvements and Refactors

Another 482 pull requests implement various fixes, improvements and refactors.

Documentation and Tests

In this release, we moved a significant part of our documentation out of the Tock kernel repository, and into the Tock book itself. Nonetheless, this release includes 43 PRs to in-kernel documentation, in addition to the documentation changes included in all other PRs.

Internal Changes

Last but not least, this release includes 206 contributions to internal documentation, tooling and CI.