From 047be751caf26735bb1de2b7d6ad296d9dbe7ce9 Mon Sep 17 00:00:00 2001 From: Ross Burton Date: Mon, 20 Feb 2023 15:48:41 +0000 Subject: [PATCH] arm/optee-os: add missing patch header Signed-off-by: Jon Mason --- .../0008-no-warn-rwx-segments.patch | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/meta-arm/recipes-security/optee/optee-os-3.19.0/0008-no-warn-rwx-segments.patch b/meta-arm/recipes-security/optee/optee-os-3.19.0/0008-no-warn-rwx-segments.patch index 2dc797b3..64a3d7e5 100644 --- a/meta-arm/recipes-security/optee/optee-os-3.19.0/0008-no-warn-rwx-segments.patch +++ b/meta-arm/recipes-security/optee/optee-os-3.19.0/0008-no-warn-rwx-segments.patch @@ -1,3 +1,24 @@ +From cf2a2451f4e9300532d677bb3a8315494a3b3a82 Mon Sep 17 00:00:00 2001 +From: Jerome Forissier +Date: Fri, 5 Aug 2022 09:48:03 +0200 +Subject: [PATCH] core: link: add --no-warn-rwx-segments + +Signed-off-by: Anton Antonov +Upstream-Status: Backport [https://github.com/OP-TEE/optee_os/pull/5474] + +binutils ld.bfd generates one RWX LOAD segment by merging several sections +with mixed R/W/X attributes (.text, .rodata, .data). After version 2.38 it +also warns by default when that happens [1], which breaks the build due to +--fatal-warnings. The RWX segment is not a problem for the TEE core, since +that information is not used to set memory permissions. Therefore, silence +the warning. + +Link: [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ba951afb99912da01a6e8434126b8fac7aa75107 +Link: https://sourceware.org/bugzilla/show_bug.cgi?id=29448 +Reported-by: Dominique Martinet +Signed-off-by: Jerome Forissier +Acked-by: Jens Wiklander + diff --git a/core/arch/arm/kernel/link.mk b/core/arch/arm/kernel/link.mk index 0e96e606c..3fbcb6804 100644 --- a/core/arch/arm/kernel/link.mk