Changes in Makefile

bfc98dbc - selftests/x86/avx: Add AVX tests

Wed, 26 Feb 2025 01:07:29 +0000

selftests/x86/avx: Add AVX testsAdd xstate testing specifically for those vector register states,validating kernel's context switching and ensuring ABI compliance.Use the established xstate testing framework.Alternatively, this invocation could be placed directly inxstate.c::main(). However, the current test file naming convention, whichclearly specifies the tested area, seems reasonable. Adding avx.cconsiderably aligns with that convention.The test output should be like this for ZMM_Hi256 as an example: $ avx_64 ... [RUN] AVX-512 ZMM_Hi256: check context switches, 10 iterations, 5 threads. [OK] No incorrect case was found. [RUN] AVX-512 ZMM_Hi256: inject xstate via ptrace(). [OK] 'xfeatures' in SW reserved area was correctly written [OK] xstate was correctly updated. [RUN] AVX-512 ZMM_Hi256: load xstate and raise SIGUSR1 [OK] 'magic1' is valid [OK] 'xfeatures' in SW reserved area is valid [OK] 'xfeatures' in XSAVE header is valid [OK] xstate delivery was successful [OK] 'magic2' is valid [RUN] AVX-512 ZMM_Hi256: load new xstate from sighandler and check it after sigreturn [OK] xstate was restored correctlyBut systems without AVX-512 will look like: ... The kernel does not support feature number: 5 The kernel does not support feature number: 6 The kernel does not support feature number: 7Signed-off-by: Chang S. Bae Signed-off-by: Ingo Molnar Link: https://lore.kernel.org/r/20250226010731.2456-10-chang.seok.bae@intel.com List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

40f6852e - selftests/x86/xstate: Refactor context switching test

Wed, 26 Feb 2025 01:07:24 +0000

selftests/x86/xstate: Refactor context switching testThe existing context switching and ptrace tests in amx.c are not specificto dynamic states, making them reusable for general xstate testing.As a first step, move the context switching test to xstate.c. Refactorthe test code to allow specifying which xstate component being tested.To decouple the test from dynamic states, remove the permission requestcode. In fact, The permission request inside the test wrapper wasredundant.Additionally, replace fatal_error() with ksft_exit_fail_msg() forconsistency in error handling. Expected output: $ amx_64 ... [RUN] AMX Tile data: check context switches, 10 iterations, 5 threads. [OK] No incorrect case was found.Signed-off-by: Chang S. Bae Signed-off-by: Ingo Molnar Link: https://lore.kernel.org/r/20250226010731.2456-5-chang.seok.bae@intel.com List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

40153505 - Documentation/srso: Document a method for checking safe RET operates properly

Wed, 31 Jul 2024 16:05:31 +0000

Documentation/srso: Document a method for checking safe RET operates properlyAdd a method to quickly verify whether safe RET operates properly ona given system using perf tool.Also, add a selftest which does the same thing.Signed-off-by: Borislav Petkov (AMD) Link: https://lore.kernel.org/r/20240731160531.28640-1-bp@kernel.org List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

a89e5890 - selftests/x86: avoid -no-pie warnings from clang during compilation

Thu, 04 Jul 2024 07:24:29 +0000

selftests/x86: avoid -no-pie warnings from clang during compilationWhen building with clang, via: make LLVM=1 -C tools/testing/selftests...clang warns that -no-pie is "unused during compilation".This occurs because clang only wants to see -no-pie during linking.Here, we don't have a separate linking stage, so a compiler warning isunavoidable without (wastefully) restructuring the Makefile.Avoid the warning by simply disabling that warning, for clang builds.Acked-by: Muhammad Usama Anjum Signed-off-by: John Hubbard Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

2ab9c93d - selftests/x86: build sysret_rip.c with clang

Thu, 04 Jul 2024 07:24:28 +0000

selftests/x86: build sysret_rip.c with clangWhen building with clang, via: make LLVM=1 -C tools/testing/selftests...the build fails because clang's inline asm doesn't support all of thefeatures that are used in the asm() snippet in sysret_rip.c.Fix this by moving the asm code into the clang_helpers_64.S file, whereit can be built with the assembler's full set of features.Acked-by: Muhammad Usama Anjum Signed-off-by: John Hubbard Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

11586553 - selftests/x86: build fsgsbase_restore.c with clang

Thu, 04 Jul 2024 07:24:27 +0000

selftests/x86: build fsgsbase_restore.c with clangWhen building with clang, via: make LLVM=1 -C tools/testing/selftestsFix this by moving the inline asm to "pure" assembly, in two new files:clang_helpers_32.S, clang_helpers_64.S.As a bonus, the pure asm avoids the need for ifdefs, and is now verysimple and easy on the eyes.Acked-by: Muhammad Usama Anjum Signed-off-by: John Hubbard Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

825658b7 - selftests/x86: fix Makefile dependencies to work with clang

Thu, 04 Jul 2024 07:24:25 +0000

selftests/x86: fix Makefile dependencies to work with clangWhen building with clang, via: make LLVM=1 -C tools/testing/selftests...the following build failure occurs in selftests/x86: clang: error: cannot specify -o when generating multiple output filesThis happens because, although gcc doesn't complain if you invoke itlike this: gcc file1.c header2.h...clang won't accept that form--it rejects the .h file(s). Also, theabove approach is inaccurate anyway, because file.c includes header2.hin this case, and the inclusion of header2.h on the invocation is anartifact of the Makefile's desire to maintain dependencies.In Makefiles of this type, a better way to do it is to use Makefiledependencies to trigger the appropriate incremental rebuilds, andseparately use file lists (see EXTRA_FILES in this commit) to track whatto pass to the compiler.This commit splits those concepts up, by setting up both EXTRA_FILES andthe Makefile dependencies with a single call to the new Makefilefunction extra-files.That fixes the build failure, while still providing the correctdependencies in all cases.Acked-by: Muhammad Usama Anjum Signed-off-by: John Hubbard Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

802e87cc - selftests/x86/mm: Add new test that userspace stack is in fact NX

Tue, 03 Oct 2023 16:18:43 +0000

selftests/x86/mm: Add new test that userspace stack is in fact NXHere is how it works: * fault and fill the stack from RSP with INT3 down until rlimit allows, * fill upwards with INT3 too, overwrite libc stuff, argv, envp, * try to exec INT3 on each page and catch it in either SIGSEGV or SIGTRAP handler.Note: trying to execute _every_ INT3 on a 8 MiB stack takes 30-40 secondseven on fast machine which is too much for kernel selftesting(not for LTP!) so only 1 INT3 per page is tried.Tested on F37 kernel and on a custom kernel which does: vm_flags |= VM_EXEC;to stack VMA.Report from the buggy kernel: $ ./nx_stack_32 stack min ff007000 stack max ff807000 FAIL executable page on the stack: eip ff806001 $ ./nx_stack_64 stack min 7ffe65bb0000 stack max 7ffe663b0000 FAIL executable page on the stack: rip 7ffe663af001Signed-off-by: Alexey Dobriyan Signed-off-by: Ingo Molnar Link: https://lore.kernel.org/r/4cef8266-ad6d-48af-a5f1-fc2b6a8eb422@p183 List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

81f30337 - selftests/x86: Add shadow stack test

Tue, 13 Jun 2023 00:11:05 +0000

selftests/x86: Add shadow stack testAdd a simple selftest for exercising some shadow stack behavior: - map_shadow_stack syscall and pivot - Faulting in shadow stack memory - Handling shadow stack violations - GUP of shadow stack memory - mprotect() of shadow stack memory - Userfaultfd on shadow stack memory - 32 bit segmentation - Guard gap test - Ptrace testCo-developed-by: Yu-cheng Yu Signed-off-by: Yu-cheng Yu Signed-off-by: Rick Edgecombe Signed-off-by: Dave Hansen Acked-by: Mike Rapoport (IBM) Tested-by: Pengfei Xu Tested-by: John Allen Tested-by: Kees Cook Link: https://lore.kernel.org/all/20230613001108.3040476-40-rick.p.edgecombe%40intel.com List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

3de9745c - selftests/x86/lam: Add malloc and tag-bits test cases for linear-address masking

Sun, 12 Mar 2023 11:26:07 +0000

selftests/x86/lam: Add malloc and tag-bits test cases for linear-address maskingLAM is supported only in 64-bit mode and applies only addresses used for dataaccesses. In 64-bit mode, linear address have 64 bits. LAM is applied to 64-bitlinear address and allow software to use high bits for metadata.LAM supports configurations that differ regarding which pointer bits are maskedand can be used for metadata.LAM includes following mode: - LAM_U57, pointer bits in positions 62:57 are masked (LAM width 6), allows bits 62:57 of a user pointer to be used as metadata.There are some arch_prctls:ARCH_ENABLE_TAGGED_ADDR: enable LAM mode, mask high bits of a user pointer.ARCH_GET_UNTAG_MASK: get current untagged mask.ARCH_GET_MAX_TAG_BITS: the maximum tag bits user can request. zero if LAMis not supported.The LAM mode is for pre-process, a process has only one chance to set LAM mode.But there is no API to disable LAM mode. So all of test cases are run underchild process.Functions of this test:MALLOC - LAM_U57 masks bits 57:62 of a user pointer. Process on user space can dereference such pointers. - Disable LAM, dereference a pointer with metadata above 48 bit or 57 bit lead to trigger SIGSEGV.TAG_BITS - Max tag bits of LAM_U57 is 6.Signed-off-by: Weihong Zhang Signed-off-by: Kirill A. Shutemov Signed-off-by: Dave Hansen Acked-by: Peter Zijlstra (Intel) Link: https://lore.kernel.org/all/20230312112612.31869-13-kirill.shutemov%40linux.intel.com List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

ac5ec90e - selftests: x86: Fix incorrect kernel headers search path

Fri, 27 Jan 2023 13:57:50 +0000

selftests: x86: Fix incorrect kernel headers search pathUse $(KHDR_INCLUDES) as lookup path for kernel headers. This preventsbuilding against kernel headers from the build environment in scenarioswhere kernel headers are installed into a specific output directory(O=...).Signed-off-by: Mathieu Desnoyers Cc: Shuah Khan Cc: linux-kselftest@vger.kernel.orgCc: Ingo Molnar Cc: # 5.18+Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

aa8ce299 - selftests: x86: add 32bit build warnings for SUSE

Thu, 24 Mar 2022 09:55:54 +0000

selftests: x86: add 32bit build warnings for SUSEIn order to successfully build all these 32bit tests, these 32bit gccand glibc packages, named gcc-32bit and glibc-devel-static-32bit on SUSE,need to be installed.This patch added this information in warn_32bit_failure.Signed-off-by: Geliang Tang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

ef696f93 - selftests, x86: fix how check_cc.sh is being invoked

Tue, 22 Mar 2022 21:41:44 +0000

selftests, x86: fix how check_cc.sh is being invokedThe $(CC) variable used in Makefiles could contain several argumentssuch as "ccache gcc". These need to be passed as a single string tocheck_cc.sh, otherwise only the first argument will be used as thecompiler command. Without quotes, the $(CC) variable is passed asdistinct arguments which causes the script to fail to build trivialprograms.Fix this by adding quotes around $(CC) when calling check_cc.sh to passthe whole string as a single argument to the script even if it hasseveral words such as "ccache gcc".Link: https://lkml.kernel.org/r/d0d460d7be0107a69e3c52477761a6fe694c1840.1646991629.git.guillaume.tucker@collabora.comFixes: e9886ace222e ("selftests, x86: Rework x86 target architecture detection")Signed-off-by: Guillaume Tucker Tested-by: "kernelci.org bot" Reviewed-by: Guenter Roeck Cc: Shuah Khan Cc: Borislav Petkov Cc: Dave Hansen Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

6a3e0651 - selftests/x86/amx: Add test cases for AMX state management

Tue, 26 Oct 2021 12:25:24 +0000

selftests/x86/amx: Add test cases for AMX state managementAMX TILEDATA is a very large XSAVE feature. It could have causednasty XSAVE buffer space waste in two places: * Signal stacks * Kernel task_struct->fpu buffersTo avoid this waste, neither of these buffers have AMX state bydefault. The non-default features are called "dynamic" features.There is an arch_prctl(ARCH_REQ_XCOMP_PERM) which allows a taskto declare that it wants to use AMX or other "dynamic" XSAVEfeatures. This arch_prctl() ensures that sufficient sigaltstackspace is available before it will succeed. It also expands thetask_struct buffer.Functions of this test: * Test arch_prctl(ARCH_REQ_XCOMP_PERM). Ensure that it checks for proper sigaltstack sizing and that the sizing is enforced for future sigaltstack calls. * Ensure that ARCH_REQ_XCOMP_PERM is inherited across fork() * Ensure that TILEDATA use before the prctl() is fatal * Ensure that TILEDATA is cleared across fork()Note: Generally, compiler support is needed to do something withAMX. Instead, directly load AMX state from userspace with aplain XSAVE. Do not depend on the compiler. [ dhansen: bunches of cleanups ]Signed-off-by: Chang S. Bae Signed-off-by: Dave Hansen Signed-off-by: Borislav Petkov Link: https://lkml.kernel.org/r/20211026122524.7BEDAA95@davehans-spike.ostc.intel.com List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

b7c11876 - selftests/x86: Test signal frame XSTATE header corruption handling

Tue, 08 Jun 2021 14:36:23 +0000

selftests/x86: Test signal frame XSTATE header corruption handlingThis is very heavily based on some code from Thomas Gleixner. On a systemwithout XSAVES, it triggers the WARN_ON(): Bad FPU state detected at copy_kernel_to_fpregs+0x2f/0x40, reinitializing FPU registers. [ bp: Massage in nitpicks. ]Signed-off-by: Andy Lutomirski Signed-off-by: Thomas Gleixner Signed-off-by: Borislav Petkov Acked-by: Dave Hansen Acked-by: Rik van Riel Link: https://lkml.kernel.org/r/20210608144346.234764986@linutronix.de List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

8919f072 - selftest/x86/signal: Include test cases for validating sigaltstack

Tue, 18 May 2021 20:03:20 +0000

selftest/x86/signal: Include test cases for validating sigaltstackThe test measures the kernel's signal delivery with different (enough vs.insufficient) stack sizes.Signed-off-by: Chang S. Bae Signed-off-by: Borislav Petkov Reviewed-by: Len Brown Acked-by: Thomas Gleixner Link: https://lkml.kernel.org/r/20210518200320.17239-7-chang.seok.bae@intel.com List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

c7e5789b - kselftest: Move test_vdso to the vDSO test suite

Mon, 26 Oct 2020 11:49:44 +0000

kselftest: Move test_vdso to the vDSO test suiteMove test_vdso from x86 to the vDSO test suite.Suggested-by: Andy Lutomirski Cc: Shuah Khan Signed-off-by: Vincenzo Frascino Acked-by: Thomas Gleixner Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

40c45904 - x86/ptrace: Fix 32-bit PTRACE_SETREGS vs fsbase and gsbase

Fri, 26 Jun 2020 17:24:29 +0000

x86/ptrace: Fix 32-bit PTRACE_SETREGS vs fsbase and gsbaseDebuggers expect that doing PTRACE_GETREGS, then poking at a traceeand maybe letting it run for a while, then doing PTRACE_SETREGS willput the tracee back where it was. In the specific case of a 32-bittracer and tracee, the PTRACE_GETREGS/SETREGS data structure doesn'thave fs_base or gs_base fields, so FSBASE and GSBASE fields arenever stored anywhere. Everything used to still work becausenonzero FS or GS would result full reloads of the segment registerswhen the tracee resumes, and the bases associated with FS==0 orGS==0 are irrelevant to 32-bit code.Adding FSGSBASE support broke this: when FSGSBASE is enabled, FSBASEand GSBASE are now restored independently of FS and GS for all taskswhen context-switched in. This means that, if a 32-bit tracerrestores a previous state using PTRACE_SETREGS but the tracee'spre-restore and post-restore bases don't match, then the tracee isresumed with the wrong base.Fix it by explicitly loading the base when a 32-bit tracer pokes FSor GS on a 64-bit kernel.Also add a test case.Fixes: 673903495c85 ("x86/process/64: Use FSBSBASE in switch_to() if available")Signed-off-by: Andy Lutomirski Signed-off-by: Thomas Gleixner Link: https://lkml.kernel.org/r/229cc6a50ecbb701abd50fe4ddaf0eda888898cd.1593192140.git.luto@kernel.org List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

cced0b24 - selftests/x86: Consolidate and fix get/set_eflags() helpers

Fri, 26 Jun 2020 17:21:16 +0000

selftests/x86: Consolidate and fix get/set_eflags() helpersThere are several copies of get_eflags() and set_eflags() and they all arebuggy. Consolidate them and fix them. The fixes are:Add memory clobbers. These are probably unnecessary but they make surethat the compiler doesn't move something past one of these calls when itshouldn't.Respect the redzone on x86_64. There has no failure been observed relatedto this, but it's definitely a bug.Signed-off-by: Andy Lutomirski Signed-off-by: Thomas Gleixner Link: https://lkml.kernel.org/r/982ce58ae8dea2f1e57093ee894760e35267e751.1593191971.git.luto@kernel.org List of files: /linux-6.15/tools/testing/selftests/x86/Makefile

804eb646 - selftests/x86/pkeys: move selftests to arch-neutral directory

Thu, 04 Jun 2020 23:51:34 +0000

selftests/x86/pkeys: move selftests to arch-neutral directoryPatch series "selftests, powerpc, x86: Memory Protection Keys", v19.Memory protection keys enables an application to protect its address spacefrom inadvertent access by its own code.This feature is now enabled on powerpc and has been available since4.16-rc1. The patches move the selftests to arch neutral directory andenhance their test coverage.Tested on powerpc64 and x86_64 (Skylake-SP).This patch (of 24):Move selftest files from tools/testing/selftests/x86/ totools/testing/selftests/vm/.Signed-off-by: Ram Pai Signed-off-by: Thiago Jung Bauermann Signed-off-by: Sandipan Das Signed-off-by: Andrew Morton Acked-by: Ingo Molnar Acked-by: Dave Hansen Cc: Dave Hansen Cc: Florian Weimer Cc: "Desnes A. Nunes do Rosario" Cc: Michal Hocko Cc: "Aneesh Kumar K.V" Cc: Michal Suchanek Cc: Michael Ellerman Cc: Shuah Khan Link: http://lkml.kernel.org/r/14d25194c3e2e652e0047feec4487e269e76e8c9.1585646528.git.sandipan@linux.ibm.comSigned-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/x86/Makefile