Changes in Makefile

e08302ee - kselftest/arm64: build BTI tests in output directory

Tue, 15 Aug 2023 14:59:31 +0000

kselftest/arm64: build BTI tests in output directoryThe arm64 BTI selftests are currently built in the source directory,then the generated binaries are copied to the output directory.This leaves the object files around in a potentially otherwise pristinesource tree, tainting it for out-of-tree kernel builds.Prepend $(OUTPUT) to every reference to an object file in the Makefile,and remove the extra handling and copying. This puts all generated filesunder the output directory.Signed-off-by: Andre Przywara Reviewed-by: Mark Brown Link: https://lore.kernel.org/r/20230815145931.2522557-1-andre.przywara@arm.comSigned-off-by: Will Deacon List of files: /linux-6.15/tools/testing/selftests/arm64/bti/Makefile

9f93c2e0 - kselftest/arm64: Explicitly build no BTI tests with BTI disabled

Mon, 16 May 2022 18:22:13 +0000

kselftest/arm64: Explicitly build no BTI tests with BTI disabledIn case a distribution enables branch protection by default do as we do forthe main kernel and explicitly disable branch protection when building thetest case for having BTI disabled to ensure it doesn't get turned on by thetoolchain defaults.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20220516182213.727589-1-broonie@kernel.orgSigned-off-by: Catalin Marinas List of files: /linux-6.15/tools/testing/selftests/arm64/bti/Makefile

d7a49291 - kselftest/arm64: bti: force static linking

Wed, 11 May 2022 17:21:29 +0000

kselftest/arm64: bti: force static linkingThe "bti" selftests are built with -nostdlib, which apparentlyautomatically creates a statically linked binary, which is what we wantand need for BTI (to avoid interactions with the dynamic linker).However this is not true when building a PIE binary, which sometoolchains (Ubuntu) configure as the default.When compiling btitest with such a toolchain, it will create adynamically linked binary, which will probably fail some tests, as thedynamic linker might not support BTI:===================TAP version 131..18not ok 1 nohint_func/call_using_br_x0not ok 2 nohint_func/call_using_br_x16not ok 3 nohint_func/call_using_blr....===================To make sure we create static binaries, add an explicit -static on thelinker command line. This forces static linking even if the toolchaindefaults to PIE builds, and fixes btitest runs on BTI enabled machines.Signed-off-by: Andre Przywara Reviewed-by: Mark Brown Fixes: 314bcbf09f14 ("kselftest: arm64: Add BTI tests")Link: https://lore.kernel.org/r/20220511172129.2078337-1-andre.przywara@arm.comSigned-off-by: Catalin Marinas List of files: /linux-6.15/tools/testing/selftests/arm64/bti/Makefile

314bcbf0 - kselftest: arm64: Add BTI tests

Tue, 09 Mar 2021 19:37:31 +0000

kselftest: arm64: Add BTI testsAdd some tests that verify that BTI functions correctly for static binariesbuilt with and without BTI support, verifying that SIGILL is generated whenexpected and is not generated in other situations.Since BTI support is still being rolled out in distributions these testsare built entirely free standing, no libc support is used at all so noneof the standard helper functions for kselftest can be used and we opencode everything. This also means we aren't testing the kernel support forthe dynamic linker, though the test program can be readily adapted forthat once it becomes something that we can reliably build and run.These tests were originally written by Dave Martin, I've adapted them forkselftest, mainly around the build system and the output format.Signed-off-by: Mark Brown Cc: Dave Martin Link: https://lore.kernel.org/r/20210309193731.57247-1-broonie@kernel.orgSigned-off-by: Catalin Marinas List of files: /linux-6.15/tools/testing/selftests/arm64/bti/Makefile