Changes in Makefile

2cbb20b0 - tracing: Disable branch profiling in noinstr code

Fri, 21 Mar 2025 19:53:32 +0000

tracing: Disable branch profiling in noinstr codeCONFIG_TRACE_BRANCH_PROFILING inserts a call to ftrace_likely_update()for each use of likely() or unlikely(). That breaks noinstr rules ifthe affected function is annotated as noinstr.Disable branch profiling for files with noinstr functions. In additionto some individual files, this also includes the entire arch/x86subtree, as well as the kernel/entry, drivers/cpuidle, and drivers/idledirectories, all of which are noinstr-heavy.Due to the nature of how sched binaries are built by combining multiple.c files into one, branch profiling is disabled more broadly across thesched code than would otherwise be needed.This fixes many warnings like the following: vmlinux.o: warning: objtool: do_syscall_64+0x40: call to ftrace_likely_update() leaves .noinstr.text section vmlinux.o: warning: objtool: __rdgsbase_inactive+0x33: call to ftrace_likely_update() leaves .noinstr.text section vmlinux.o: warning: objtool: handle_bug.isra.0+0x198: call to ftrace_likely_update() leaves .noinstr.text section ...Reported-by: Ingo Molnar Suggested-by: Steven Rostedt Signed-off-by: Josh Poimboeuf Signed-off-by: Ingo Molnar Acked-by: Thomas Gleixner Cc: Linus Torvalds Link: https://lore.kernel.org/r/fb94fc9303d48a5ed370498f54500cc4c338eb6d.1742586676.git.jpoimboe@kernel.org List of files: /linux-6.15/kernel/Makefile

0e8b6798 - mm: move kernel/numa.c to mm/

Wed, 07 Aug 2024 06:40:45 +0000

mm: move kernel/numa.c to mm/Patch series "mm: introduce numa_memblks", v4.Following the discussion about handling of CXL fixed memory windows onarm64 [1] I decided to bite the bullet and move numa_memblks from x86 tothe generic code so they will be available on arm64/riscv and maybe onloongarch sometime later.While it could be possible to use memblock to describe CXL memory windows,it currently lacks notion of unpopulated memory ranges and numa_memblksdoes implement this.Another reason to make numa_memblks generic is that both arch_numa (arm64and riscv) and loongarch use trimmed copy of x86 code although there is nofundamental reason why the same code cannot be used on all theseplatforms. Having numa_memblks in mm/ will make it's interaction withACPI and FDT more consistent and I believe will reduce maintenance burden.And with generic numa_memblks it is (almost) straightforward to enableNUMA emulation on arm64 and riscv.The first 9 commits in this series are cleanups that are not strictlyrelated to numa_memblks.Commits 10-16 slightly reorder code in x86 to allow extracting numa_memblksand NUMA emulation to the generic code.Commits 17-19 actually move the code from arch/x86/ to mm/ and commits 20-22does some aftermath cleanups.Commit 23 updates of_numa_init() to return error of no NUMA nodes werefound in the device tree.Commit 24 switches arch_numa to numa_memblks.Commit 25 enables usage of phys_to_target_node() andmemory_add_physaddr_to_nid() with numa_memblks.Commit 26 moves the description for numa=fake from x86 to admin-guide.[1] https://lore.kernel.org/all/20240529171236.32002-1-Jonathan.Cameron@huawei.com/This patch (of 26):The stub functions in kernel/numa.c belong to mm/ rather than to kernel/Link: https://lkml.kernel.org/r/20240807064110.1003856-1-rppt@kernel.orgLink: https://lkml.kernel.org/r/20240807064110.1003856-2-rppt@kernel.orgSigned-off-by: Mike Rapoport (Microsoft) Acked-by: David Hildenbrand Reviewed-by: Jonathan Cameron Tested-by: Zi Yan # for x86_64 and arm64Tested-by: Jonathan Cameron [arm64 + CXL via QEMU]Acked-by: Dan Williams Cc: Alexander Gordeev Cc: Andreas Larsson Cc: Arnd Bergmann Cc: Borislav Petkov Cc: Catalin Marinas Cc: Christophe Leroy Cc: Dave Hansen Cc: Davidlohr Bueso Cc: David S. Miller Cc: Greg Kroah-Hartman Cc: Heiko Carstens Cc: Huacai Chen Cc: Ingo Molnar Cc: Jiaxun Yang Cc: John Paul Adrian Glaubitz Cc: Jonathan Corbet Cc: Michael Ellerman Cc: Palmer Dabbelt Cc: Rafael J. Wysocki Cc: Rob Herring (Arm) Cc: Samuel Holland Cc: Thomas Bogendoerfer Cc: Thomas Gleixner Cc: Vasily Gorbik Cc: Will Deacon Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

02aff848 - crash: split crash dumping code out from kexec_core.c

Wed, 24 Jan 2024 05:12:44 +0000

crash: split crash dumping code out from kexec_core.cCurrently, KEXEC_CORE select CRASH_CORE automatically because crash codesneed be built in to avoid compiling error when building kexec code eventhough the crash dumping functionality is not enabled. E.g--------------------CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_KEXEC=yCONFIG_KEXEC_FILE=y---------------------After splitting out crashkernel reservation code and vmcoreinfo exportingcode, there's only crash related code left in kernel/crash_core.c. Nowmove crash related codes from kexec_core.c to crash_core.c and only build itin when CONFIG_CRASH_DUMP=y.And also wrap up crash codes inside CONFIG_CRASH_DUMP ifdeffery scope,or replace inappropriate CONFIG_KEXEC_CORE ifdef with CONFIG_CRASH_DUMPifdef in generic kernel files.With these changes, crash_core codes are abstracted from kexec codes andcan be disabled at all if only kexec reboot feature is wanted.Link: https://lkml.kernel.org/r/20240124051254.67105-5-bhe@redhat.comSigned-off-by: Baoquan He Cc: Al Viro Cc: Eric W. Biederman Cc: Hari Bathini Cc: Pingfan Liu Cc: Klara Modin Cc: Michael Kelley Cc: Nathan Chancellor Cc: Stephen Rothwell Cc: Yang Li Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

2c44b67e - crash: remove dependency of FA_DUMP on CRASH_DUMP

Wed, 24 Jan 2024 05:12:43 +0000

crash: remove dependency of FA_DUMP on CRASH_DUMPIn kdump kernel, /proc/vmcore is an elf file mapping the crashed kernel'sold memory content. Its elf header is constructed in 1st kernel and passedto kdump kernel via elfcorehdr_addr. Config CRASH_DUMP enables the codeof 1st kernel's old memory accessing in different architectures.Currently, config FA_DUMP has dependency on CRASH_DUMP because fadumpneeds access global variable 'elfcorehdr_addr' to judge if it's inkdump kernel within function is_kdump_kernel(). In the currentkernel/crash_dump.c, variable 'elfcorehdr_addr' is defined, and functionsetup_elfcorehdr() used to parse kernel parameter to fetch the passedvalue of elfcorehdr_addr. Only for accessing elfcorehdr_addr, FA_DUMPreally doesn't have to depends on CRASH_DUMP.To remove the dependency of FA_DUMP on CRASH_DUMP to avoid confusion,rename kernel/crash_dump.c to kernel/elfcorehdr.c, and build it whenCONFIG_VMCORE_INFO is ebabled. With this, FA_DUMP doesn't need to dependon CRASH_DUMP.[bhe@redhat.com: power/fadump: make FA_DUMP select CRASH_DUMP] Link: https://lkml.kernel.org/r/Zb8D1ASrgX0qVm9z@MiWiFi-R3L-srvLink: https://lkml.kernel.org/r/20240124051254.67105-4-bhe@redhat.comSigned-off-by: Baoquan He Acked-by: Hari Bathini Cc: Al Viro Cc: Eric W. Biederman Cc: Pingfan Liu Cc: Klara Modin Cc: Michael Kelley Cc: Nathan Chancellor Cc: Stephen Rothwell Cc: Yang Li Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

443cbaf9 - crash: split vmcoreinfo exporting code out from crash_core.c

Wed, 24 Jan 2024 05:12:42 +0000

crash: split vmcoreinfo exporting code out from crash_core.cNow move the relevant codes into separate files:kernel/crash_reserve.c, include/linux/crash_reserve.h.And add config item CRASH_RESERVE to control its enabling.And also update the old ifdeffery of CONFIG_CRASH_CORE, including of and config item dependency on CRASH_COREaccordingly.And also do renaming as follows: - arch/xxx/kernel/{crash_core.c => vmcore_info.c}because they are only related to vmcoreinfo exporting on x86, arm64,riscv.And also Remove config item CRASH_CORE, and rely on CONFIG_KEXEC_CORE todecide if build in crash_core.c.[yang.lee@linux.alibaba.com: remove duplicated include in vmcore_info.c] Link: https://lkml.kernel.org/r/20240126005744.16561-1-yang.lee@linux.alibaba.comLink: https://lkml.kernel.org/r/20240124051254.67105-3-bhe@redhat.comSigned-off-by: Baoquan He Signed-off-by: Yang Li Acked-by: Hari Bathini Cc: Al Viro Cc: Eric W. Biederman Cc: Pingfan Liu Cc: Klara Modin Cc: Michael Kelley Cc: Nathan Chancellor Cc: Stephen Rothwell Cc: Yang Li Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

85fcde40 - kexec: split crashkernel reservation code out from crash_core.c

Wed, 24 Jan 2024 05:12:41 +0000

kexec: split crashkernel reservation code out from crash_core.cPatch series "Split crash out from kexec and clean up related configitems", v3.Motivation:=============Previously, LKP reported a building error. When investigating, it can'tbe resolved reasonablly with the present messy kdump config items. https://lore.kernel.org/oe-kbuild-all/202312182200.Ka7MzifQ-lkp@intel.com/The kdump (crash dumping) related config items could causes confusions:Firstly,CRASH_CORE enables codes including - crashkernel reservation; - elfcorehdr updating; - vmcoreinfo exporting; - crash hotplug handling;Now fadump of powerpc, kcore dynamic debugging and kdump all selectsCRASH_CORE, while fadump - fadump needs crashkernel parsing, vmcoreinfo exporting, and accessing global variable 'elfcorehdr_addr'; - kcore only needs vmcoreinfo exporting; - kdump needs all of the current kernel/crash_core.c.So only enabling PROC_CORE or FA_DUMP will enable CRASH_CORE, thismislead people that we enable crash dumping, actual it's not.Secondly,It's not reasonable to allow KEXEC_CORE select CRASH_CORE.Because KEXEC_CORE enables codes which allocate control pages, copykexec/kdump segments, and prepare for switching. These codes areshared by both kexec reboot and kdump. We could want kexec reboot,but disable kdump. In that case, CRASH_CORE should not be selected. -------------------- CONFIG_CRASH_CORE=y CONFIG_KEXEC_CORE=y CONFIG_KEXEC=y CONFIG_KEXEC_FILE=y ---------------------Thirdly,It's not reasonable to allow CRASH_DUMP select KEXEC_CORE.That could make KEXEC_CORE, CRASH_DUMP are enabled independently fromKEXEC or KEXEC_FILE. However, w/o KEXEC or KEXEC_FILE, the KEXEC_COREcode built in doesn't make any sense because no kernel loading orswitching will happen to utilize the KEXEC_CORE code. --------------------- CONFIG_CRASH_CORE=y CONFIG_KEXEC_CORE=y CONFIG_CRASH_DUMP=y ---------------------In this case, what is worse, on arch sh and arm, KEXEC relies on MMU,while CRASH_DUMP can still be enabled when !MMU, then compiling error isseen as the lkp test robot reported in above link. ------arch/sh/Kconfig------ config ARCH_SUPPORTS_KEXEC def_bool MMU config ARCH_SUPPORTS_CRASH_DUMP def_bool BROKEN_ON_SMP ---------------------------Changes:===========1, split out crash_reserve.c from crash_core.c;2, split out vmcore_infoc. from crash_core.c;3, move crash related codes in kexec_core.c into crash_core.c;4, remove dependency of FA_DUMP on CRASH_DUMP;5, clean up kdump related config items;6, wrap up crash codes in crash related ifdefs on all 8 arch-es which support crash dumping, except of ppc;Achievement:===========With above changes, I can rearrange the config item logic as below (the rightitem depends on or is selected by the left item): PROC_KCORE -----------> VMCORE_INFO |----------> VMCORE_INFO FA_DUMP----| |----------> CRASH_RESERVE ---->VMCORE_INFO / |---->CRASH_RESERVE KEXEC --| /| |--> KEXEC_CORE--> CRASH_DUMP-->/-|---->PROC_VMCORE KEXEC_FILE --| \ | \---->CRASH_HOTPLUG KEXEC --| |--> KEXEC_CORE (for kexec reboot only) KEXEC_FILE --|Test========On all 8 architectures, including x86_64, arm64, s390x, sh, arm, mips,riscv, loongarch, I did below three cases of config item setting andbuilding all passed. Take configs on x86_64 as exampmle here:(1) Both CONFIG_KEXEC and KEXEC_FILE is unset, then all kexec/kdumpitems are unset automatically:# Kexec and crash features# CONFIG_KEXEC is not set# CONFIG_KEXEC_FILE is not set# end of Kexec and crash features(2) set CONFIG_KEXEC_FILE and 'make olddefconfig':---------------# Kexec and crash featuresCONFIG_CRASH_RESERVE=yCONFIG_VMCORE_INFO=yCONFIG_KEXEC_CORE=yCONFIG_KEXEC_FILE=yCONFIG_CRASH_DUMP=yCONFIG_CRASH_HOTPLUG=yCONFIG_CRASH_MAX_MEMORY_RANGES=8192# end of Kexec and crash features---------------(3) unset CONFIG_CRASH_DUMP in case 2 and execute 'make olddefconfig':------------------------# Kexec and crash featuresCONFIG_KEXEC_CORE=yCONFIG_KEXEC_FILE=y# end of Kexec and crash features------------------------Note:For ppc, it needs investigation to make clear how to split out crashcode in arch folder. Hope Hari and Pingfan can help have a look, see ifit's doable. Now, I make it either have both kexec and crash enabled, ordisable both of them altogether.This patch (of 14):Both kdump and fa_dump of ppc rely on crashkernel reservation. Move therelevant codes into separate files: crash_reserve.c,include/linux/crash_reserve.h.And also add config item CRASH_RESERVE to control its enabling of thecodes. And update config items which has relationship with crashkernelreservation.And also change ifdeffery from CONFIG_CRASH_CORE to CONFIG_CRASH_RESERVEwhen those scopes are only crashkernel reservation related.And also rename arch/XXX/include/asm/{crash_core.h => crash_reserve.h} onarm64, x86 and risc-v because those architectures' crash_core.h is onlyrelated to crashkernel reservation.[akpm@linux-foundation.org: s/CRASH_RESEERVE/CRASH_RESERVE/, per Klara Modin]Link: https://lkml.kernel.org/r/20240124051254.67105-1-bhe@redhat.comLink: https://lkml.kernel.org/r/20240124051254.67105-2-bhe@redhat.comSigned-off-by: Baoquan He Acked-by: Hari Bathini Cc: Al Viro Cc: Eric W. Biederman Cc: Pingfan Liu Cc: Klara Modin Cc: Michael Kelley Cc: Nathan Chancellor Cc: Stephen Rothwell Cc: Yang Li Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

d7a73e3f - kernel/numa.c: Move logging out of numa.h

Mon, 11 Dec 2023 18:27:00 +0000

kernel/numa.c: Move logging out of numa.hMoving these stub functions to a .c file means we can kill a sched.hdependency on printk.h.Signed-off-by: Kent Overstreet List of files: /linux-6.15/kernel/Makefile

1f423c90 - watchdog/hardlockup: detect hard lockups using secondary (buddy) CPUs

Fri, 19 May 2023 17:18:38 +0000

watchdog/hardlockup: detect hard lockups using secondary (buddy) CPUsImplement a hardlockup detector that doesn't doesn't need any extraarch-specific support code to detect lockups. Instead of using somethingarch-specific we will use the buddy system, where each CPU watches out foranother one. Specifically, each CPU will use its softlockup hrtimer tocheck that the next CPU is processing hrtimer interrupts by verifying thata counter is increasing.NOTE: unlike the other hard lockup detectors, the buddy one can't easilyshow what's happening on the CPU that locked up just by doing a simplebacktrace. It relies on some other mechanism in the system to getinformation about the locked up CPUs. This could be support for NMIbacktraces like [1], it could be a mechanism for printing the PC of lockedCPUs at panic time like [2] / [3], or it could be something else. Eventhough that means we still rely on arch-specific code, this arch-specificcode seems to often be implemented even on architectures that don't have ahardlockup detector.This style of hardlockup detector originated in some downstream Androidtrees and has been rebased on / carried in ChromeOS trees for quite a longtime for use on arm and arm64 boards. Historically on these boards we'veleveraged mechanism [2] / [3] to get information about hung CPUs, but wecould move to [1].Although the original motivation for the buddy system was for use onsystems without an arch-specific hardlockup detector, it can still beuseful to use even on systems that _do_ have an arch-specific hardlockupdetector. On x86, for instance, there is a 24-part patch series [4] inprogress switching the arch-specific hard lockup detector from a scarceperf counter to a less-scarce hardware resource. Potentially the buddysystem could be a simpler alternative to free up the perf counter butstill get hard lockup detection.Overall, pros (+) and cons (-) of the buddy system compared to anarch-specific hardlockup detector (which might be implemented usingperf):+ The buddy system is usable on systems that don't have an arch-specific hardlockup detector, like arm32 and arm64 (though it's being worked on for arm64 [5]).+ The buddy system may free up scarce hardware resources.+ If a CPU totally goes out to lunch (can't process NMIs) the buddy system could still detect the problem (though it would be unlikely to be able to get a stack trace).+ The buddy system uses the same timer function to pet the hardlockup detector on the running CPU as it uses to detect hardlockups on other CPUs. Compared to other hardlockup detectors, this means it generates fewer interrupts and thus is likely better able to let CPUs stay idle longer.- If all CPUs are hard locked up at the same time the buddy system can't detect it.- If we don't have SMP we can't use the buddy system.- The buddy system needs an arch-specific mechanism (possibly NMI backtrace) to get info about the locked up CPU.[1] https://lore.kernel.org/r/20230419225604.21204-1-dianders@chromium.org[2] https://issuetracker.google.com/172213129[3] https://docs.kernel.org/trace/coresight/coresight-cpu-debug.html[4] https://lore.kernel.org/lkml/20230301234753.28582-1-ricardo.neri-calderon@linux.intel.com/[5] https://lore.kernel.org/linux-arm-kernel/20220903093415.15850-1-lecopzer.chen@mediatek.com/Link: https://lkml.kernel.org/r/20230519101840.v5.14.I6bf789d21d0c3d75d382e7e51a804a7a51315f2c@changeidSigned-off-by: Colin Cross Signed-off-by: Matthias Kaehlcke Signed-off-by: Guenter Roeck Signed-off-by: Tzung-Bi Shih Signed-off-by: Douglas Anderson Cc: Andi Kleen Cc: Catalin Marinas Cc: Chen-Yu Tsai Cc: Christophe Leroy Cc: Daniel Thompson Cc: "David S. Miller" Cc: Ian Rogers Cc: Marc Zyngier Cc: Mark Rutland Cc: Masayoshi Mizuma Cc: Michael Ellerman Cc: Nicholas Piggin Cc: Petr Mladek Cc: Pingfan Liu Cc: Randy Dunlap Cc: "Ravi V. Shankar" Cc: Ricardo Neri Cc: Stephane Eranian Cc: Stephen Boyd Cc: Sumit Garg Cc: Will Deacon Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

6ea0d042 - watchdog/perf: rename watchdog_hld.c to watchdog_perf.c

Fri, 19 May 2023 17:18:31 +0000

watchdog/perf: rename watchdog_hld.c to watchdog_perf.cThe code currently in "watchdog_hld.c" is for detecting hardlockups usingperf, as evidenced by the line in the Makefile that only compiles thisfile if CONFIG_HARDLOCKUP_DETECTOR_PERF is defined. Rename the file toprepare for the buddy hardlockup detector, which doesn't use perf.It could be argued that the new name makes it less obvious that this is ahardlockup detector. While true, it's not hard to remember that the"perf" detector is always a hardlockup detector and it's nice not to havenames that are too convoluted.Link: https://lkml.kernel.org/r/20230519101840.v5.7.Ice803cb078d0e15fb2cbf49132f096ee2bd4199d@changeidSigned-off-by: Douglas Anderson Acked-by: Nicholas Piggin Reviewed-by: Petr Mladek Cc: Andi Kleen Cc: Catalin Marinas Cc: Chen-Yu Tsai Cc: Christophe Leroy Cc: Colin Cross Cc: Daniel Thompson Cc: "David S. Miller" Cc: Guenter Roeck Cc: Ian Rogers Cc: Lecopzer Chen Cc: Marc Zyngier Cc: Mark Rutland Cc: Masayoshi Mizuma Cc: Matthias Kaehlcke Cc: Michael Ellerman Cc: Pingfan Liu Cc: Randy Dunlap Cc: "Ravi V. Shankar" Cc: Ricardo Neri Cc: Stephane Eranian Cc: Stephen Boyd Cc: Sumit Garg Cc: Tzung-Bi Shih Cc: Will Deacon Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

b06e9318 - kallsyms: move kallsyms_show_value() out of kallsyms.c

Thu, 08 Jun 2023 03:31:18 +0000

kallsyms: move kallsyms_show_value() out of kallsyms.cfunction kallsyms_show_value() is used by other partslike modules_open(), kprobes_read() etc. which can work in case of!KALLSYMS also.e.g. as of now lsmod do not show module address if KALLSYMS is disabled.since kallsyms_show_value() defination is not present, it returns falsein !KALLSYMS./ # lsmodtest 12288 0 - Live 0x0000000000000000 (O)So kallsyms_show_value() can be made genericwithout dependency on KALLSYMS.Thus moving out function to a new file ksyms_common.c.With this patch code is just moved to new fileand no functional change.Co-developed-by: Onkarnath Signed-off-by: Onkarnath Signed-off-by: Maninder Singh Reviewed-by: Zhen Lei Signed-off-by: Luis Chamberlain List of files: /linux-6.15/kernel/Makefile

25be451a - module: fold usermode helper kmod into modules directory

Sun, 19 Mar 2023 21:35:42 +0000

module: fold usermode helper kmod into modules directoryThe kernel/kmod.c is already only built if we enabled modules, sojust stuff it under kernel/module/kmod.c and unify the MAINTAINERSfile for it.Signed-off-by: Luis Chamberlain List of files: /linux-6.15/kernel/Makefile

e297cd54 - vhost_task: Allow vhost layer to use copy_process

Fri, 10 Mar 2023 22:03:30 +0000

vhost_task: Allow vhost layer to use copy_processQemu will create vhost devices in the kernel which perform network, SCSI,etc IO and management operations from worker threads created by thekthread API. Because the kthread API does a copy_process on the kthreaddthread, the vhost layer has to use kthread_use_mm to access the Qemuthread's memory and cgroup_attach_task_all to add itself to the Qemuthread's cgroups, and it bypasses the RLIMIT_NPROC limit which can resultin VMs creating more threads than the admin expected.This patch adds a new struct vhost_task which can be used instead ofkthreads. They allow the vhost layer to use copy_process and inheritthe userspace process's mm and cgroups, the task is accounted forunder the userspace's nproc count and can be seen in its process tree,and other features like namespaces work and are inherited by default.Signed-off-by: Mike Christie Acked-by: Michael S. Tsirkin Signed-off-by: Christian Brauner (Microsoft) Signed-off-by: Christian Brauner List of files: /linux-6.15/kernel/Makefile

cf801640 - cfi: Fix CFI failure with KASAN

Thu, 22 Dec 2022 22:57:47 +0000

cfi: Fix CFI failure with KASANWhen CFI_CLANG and KASAN are both enabled, LLVM doesn't generate aCFI type hash for asan.module_ctor functions in translation unitswhere CFI is disabled, which leads to a CFI failure during boot whendo_ctors calls the affected constructors: CFI failure at do_basic_setup+0x64/0x90 (target: asan.module_ctor+0x0/0x28; expected type: 0xa540670c)Specifically, this happens because CFI is disabled forkernel/cfi.c. There's no reason to keep CFI disabled here anymore, sofix the failure by not filtering out CC_FLAGS_CFI for the file.Note that https://reviews.llvm.org/rG3b14862f0a96 fixed the issuewhere LLVM didn't emit CFI type hashes for any sanitizer constructors,but now type hashes are emitted correctly for TUs that use CFI.Link: https://github.com/ClangBuiltLinux/linux/issues/1742Fixes: 89245600941e ("cfi: Switch to -fsanitize=kcfi")Reported-by: Mark Rutland Signed-off-by: Sami Tolvanen Signed-off-by: Kees Cook Link: https://lore.kernel.org/r/20221222225747.3538676-1-samitolvanen@google.com List of files: /linux-6.15/kernel/Makefile

30f3bb09 - kallsyms: Add self-test facility

Tue, 15 Nov 2022 08:33:48 +0000

kallsyms: Add self-test facilityAdded test cases for basic functions and performance of functionskallsyms_lookup_name(), kallsyms_on_each_symbol() andkallsyms_on_each_match_symbol(). It also calculates the compression rateof the kallsyms compression algorithm for the current symbol set.The basic functions test begins by testing a set of symbols whose addressvalues are known. Then, traverse all symbol addresses and find thecorresponding symbol name based on the address. It's impossible todetermine whether these addresses are correct, but we can use the abovethree functions along with the addresses to test each other. Due to thetraversal operation of kallsyms_on_each_symbol() is too slow, only 60symbols can be tested in one second, so let it test on average onceevery 128 symbols. The other two functions validate all symbols.If the basic functions test is passed, print only performance testresults. If the test fails, print error information, but do not performsubsequent performance tests.Start self-test automatically after system startup ifCONFIG_KALLSYMS_SELFTEST=y.Example of output content: (prefix 'kallsyms_selftest:' is omitted start --------------------------------------------------------- | nr_symbols | compressed size | original size | ratio(%) | |---------------------------------------------------------| | 107543 | 1357912 | 2407433 | 56.40 | --------------------------------------------------------- kallsyms_lookup_name() looked up 107543 symbols The time spent on each symbol is (ns): min=630, max=35295, avg=7353 kallsyms_on_each_symbol() traverse all: 11782628 ns kallsyms_on_each_match_symbol() traverse all: 9261 ns finishSigned-off-by: Zhen Lei Signed-off-by: Luis Chamberlain List of files: /linux-6.15/kernel/Makefile

79dbd006 - kmsan: disable instrumentation of unsupported common kernel code

Thu, 15 Sep 2022 15:03:46 +0000

kmsan: disable instrumentation of unsupported common kernel codeEFI stub cannot be linked with KMSAN runtime, so we disableinstrumentation for it.Instrumenting kcov, stackdepot or lockdep leads to infinite recursioncaused by instrumentation hooks calling instrumented code again.Link: https://lkml.kernel.org/r/20220915150417.722975-13-glider@google.comSigned-off-by: Alexander Potapenko Reviewed-by: Marco Elver Cc: Alexander Viro Cc: Alexei Starovoitov Cc: Andrey Konovalov Cc: Andrey Konovalov Cc: Andy Lutomirski Cc: Arnd Bergmann Cc: Borislav Petkov Cc: Christoph Hellwig Cc: Christoph Lameter Cc: David Rientjes Cc: Dmitry Vyukov Cc: Eric Biggers Cc: Eric Biggers Cc: Eric Dumazet Cc: Greg Kroah-Hartman Cc: Herbert Xu Cc: Ilya Leoshkevich Cc: Ingo Molnar Cc: Jens Axboe Cc: Joonsoo Kim Cc: Kees Cook Cc: Mark Rutland Cc: Matthew Wilcox Cc: Michael S. Tsirkin Cc: Pekka Enberg Cc: Peter Zijlstra Cc: Petr Mladek Cc: Stephen Rothwell Cc: Steven Rostedt Cc: Thomas Gleixner Cc: Vasily Gorbik Cc: Vegard Nossum Cc: Vlastimil Babka Signed-off-by: Andrew Morton List of files: /linux-6.15/kernel/Makefile

a870544c - kernel: remove platform_has() infrastructure

Wed, 22 Jun 2022 06:38:37 +0000

kernel: remove platform_has() infrastructureThe only use case of the platform_has() infrastructure has beenremoved again, so remove the whole feature.Signed-off-by: Juergen Gross Tested-by: Oleksandr Tyshchenko # Arm64 guest using XenReviewed-by: Stefano Stabellini Link: https://lore.kernel.org/r/20220622063838.8854-3-jgross@suse.comSigned-off-by: Juergen Gross List of files: /linux-6.15/kernel/Makefile

2130a790 - kernel: add platform_has() infrastructure

Thu, 02 Jun 2022 13:05:26 +0000

kernel: add platform_has() infrastructureAdd a simple infrastructure for setting, resetting and queryingplatform feature flags.Flags can be either global or architecture specific.Signed-off-by: Juergen Gross Reviewed-by: Oleksandr Tyshchenko Tested-by: Oleksandr Tyshchenko # Arm64 onlyReviewed-by: Christoph Hellwig Acked-by: Borislav Petkov Signed-off-by: Juergen Gross List of files: /linux-6.15/kernel/Makefile

8fd4ddda - static_call: Don't make __static_call_return0 static

Mon, 14 Mar 2022 11:49:36 +0000

static_call: Don't make __static_call_return0 staticSystem.map shows that vmlinux contains several instances of__static_call_return0(): c0004fc0 t __static_call_return0 c0011518 t __static_call_return0 c00d8160 t __static_call_return0arch_static_call_transform() uses the middle one to check whether we aresetting a call to __static_call_return0 or not: c0011520 : c0011520: 3d 20 c0 01 lis r9,-16383 <== r9 = 0xc001 << 16 c0011524: 39 29 15 18 addi r9,r9,5400 <== r9 += 0x1518 c0011528: 7c 05 48 00 cmpw r5,r9 <== r9 has value 0xc0011518 hereSo if static_call_update() is called with one of the other instances of__static_call_return0(), arch_static_call_transform() won't recognise it.In order to work properly, global single instance of __static_call_return0() is required.Fixes: 3f2a8fc4b15d ("static_call/x86: Add __static_call_return0()")Signed-off-by: Christophe Leroy Signed-off-by: Peter Zijlstra (Intel) Acked-by: Josh Poimboeuf Link: https://lkml.kernel.org/r/30821468a0e7d28251954b578e5051dc09300d04.1647258493.git.christophe.leroy@csgroup.eu List of files: /linux-6.15/kernel/Makefile

cfc1d277 - module: Move all into module/

Tue, 22 Mar 2022 14:03:31 +0000

module: Move all into module/No functional changes.This patch moves all module related code into a separate directory,modifies each file name and creates a new Makefile. Note: this effortis in preparation to refactor core module code.Reviewed-by: Christophe Leroy Signed-off-by: Aaron Tomlin Signed-off-by: Luis Chamberlain List of files: /linux-6.15/kernel/Makefile

73f9b911 - kprobes: Use rethook for kretprobe if possible

Sat, 26 Mar 2022 02:27:05 +0000

kprobes: Use rethook for kretprobe if possibleUse rethook for kretprobe function return hooking if the arch setsCONFIG_HAVE_RETHOOK=y. In this case, CONFIG_KRETPROBE_ON_RETHOOK isset to 'y' automatically, and the kretprobe internal data fieldsswitches to use rethook. If not, it continues to use kretprobespecific function return hooks.Suggested-by: Peter Zijlstra Signed-off-by: Masami Hiramatsu Signed-off-by: Alexei Starovoitov Link: https://lore.kernel.org/bpf/164826162556.2455864.12255833167233452047.stgit@devnote2 List of files: /linux-6.15/kernel/Makefile