From d800ccc6444113313741e4164b47dfbe032b41ff Mon Sep 17 00:00:00 2001 From: Carles Cufi Date: Mon, 22 Aug 2022 18:38:16 +0200 Subject: [PATCH] blobs: Introduce TAINT and TAINT_BLOBS Kconfig options In order to ensure that builds properly reflect the use of binary blobs, it is important to markt the build as tainted. For that purpose introduce two new Kconfig options that ultimately will be reflected in the build image itself. Signed-off-by: Carles Cufi --- Kconfig.zephyr | 6 ++++++ modules/Kconfig | 7 +++++++ 2 files changed, 13 insertions(+) diff --git a/Kconfig.zephyr b/Kconfig.zephyr index c45a2402a548b8..e7b6ade16c5800 100644 --- a/Kconfig.zephyr +++ b/Kconfig.zephyr @@ -630,6 +630,12 @@ config WARN_EXPERIMENTAL Print a warning when the Kconfig tree is parsed if any experimental features are enabled. +config TAINT + bool + help + Symbol that must be selected by a feature or module if the Zephyr + build is considered tainted. + config ENFORCE_ZEPHYR_STDINT bool prompt "Enforce Zephyr convention for stdint" diff --git a/modules/Kconfig b/modules/Kconfig index 220f2d657ad08d..3f046ed1e36644 100644 --- a/modules/Kconfig +++ b/modules/Kconfig @@ -1,6 +1,13 @@ # Copyright (c) 2019 Intel Corporation # SPDX-License-Identifier: Apache-2.0 +config TAINT_BLOBS + bool + select TAINT + help + This option is selected when binary blobs are present locally at + build time to reflect that the build might have been tainted by them. + comment "Available modules." osource "$(KCONFIG_BINARY_DIR)/Kconfig.modules"