The multi_v7_defconfig file provides the initial support for this
machine but it also provides a good set of extra configs unrelated to
qemu. Some even generate build warnings due to some configs being
dependent on some that are not enabled. As an initial solution we pull
the defconfig in the layer and drop the problematic (warning generating)
configs. The plan is to drop it in the future for a config fragment for
qemu efi boot and reuse the existing BSP configuration from
yocto-kernel-cache of the equivalent qemuarm machine.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Luca Seritan <luca.seritan@huawei.com>

Andrei Gherzan authored 2 years ago and Stefan Schmidt committed 2 years ago

The 5.10.109 version of linux-yocto comes with this patch included.
Avoid build error on trying to apply this patch on the linux-yocto*
recipes. Let the patch only apply to linux-oniro.

Fixes #546



Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

RAUC recommends using the "verity" format for update bundles.
Those put additional requirements on available kernel features.

Use configuration recommended by RAUC documentation setting:
CONFIG_{MD,BLK_DEV_{DM,LOOP},DM_VERITY,SQUASHFS}=y.

Closes: https://git.ostc-eu.org/distro/oniro/-/issues/157


Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

This change is in line with the project's rebranding.

The collection is also changed a bit to drop the "meta-" prefix. There
is no clear standardization on the collection name. Some use an ID, some
use ID-layer, some use meta-ID etc. We have decided to use the the layer
name without the "meta-" prefix  because this is an ID, not a layer per
se.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Followed up the project rename in the unified linux tree recipe.
Remaining change is the rename of the branch in the kernel repo and the
follow up change here.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

This rename also better reflects the purpose of the file since it
reflects ASOS kernel policies.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

The root filesystem defaults to squashfs.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Document and add gcc plugin based hardening options

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Fix building the kernel's gcc plugins with gcc 11.x - gcc 11.x needs
constexpr (hence -std=gnu++11 or higher), and the check for gcc
plugin support needs modifications (or simple disabling, given in
our context, we know gcc has plugin support).

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Marta Rybczynska authored 3 years ago and Davide Ricci committed 3 years ago

Add kernel hardening options based on the Kernel Self Protection Project
recommendations [1] and set them in the default kernel.

[1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings



Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>

For qemuarm  builds we have seen the case that ths gcc plugins build
inside the linux kernel has been failing on missing header files gmp.h,
mcp.h and others. The native dependencies have been available, but the
kernel Makefile did not have the correct include path for the headers.

Neither poky dunfell nor master has this problem. No upstreaming needed.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/93



Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Due to a configuration bug in upstream, the build system outputs a
configuration warning similar to:

---------- CONFIG_SERIAL_OF_PLATFORM -----------------
Config: CONFIG_SERIAL_OF_PLATFORM
From:
[...]/tmp/work-shared/qemux86-64/kernel-source/.kernel-meta/configs/v5.10/standard/cfg/8250.cfg
Requested value:  CONFIG_SERIAL_OF_PLATFORM=y
Actual value:

Avoid this by disabling the specific config.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>