1# SPDX-License-Identifier: GPL-2.0 2# 3# General architecture dependent options 4# 5 6# 7# Note: arch/$(SRCARCH)/Kconfig needs to be included first so that it can 8# override the default values in this file. 9# 10source "arch/$(SRCARCH)/Kconfig" 11 12menu "General architecture-dependent options" 13 14config CRASH_CORE 15 bool 16 17config KEXEC_CORE 18 select CRASH_CORE 19 bool 20 21config KEXEC_ELF 22 bool 23 24config HAVE_IMA_KEXEC 25 bool 26 27config HOTPLUG_SMT 28 bool 29 30config GENERIC_ENTRY 31 bool 32 33config KPROBES 34 bool "Kprobes" 35 depends on MODULES 36 depends on HAVE_KPROBES 37 select KALLSYMS 38 help 39 Kprobes allows you to trap at almost any kernel address and 40 execute a callback function. register_kprobe() establishes 41 a probepoint and specifies the callback. Kprobes is useful 42 for kernel debugging, non-intrusive instrumentation and testing. 43 If in doubt, say "N". 44 45config JUMP_LABEL 46 bool "Optimize very unlikely/likely branches" 47 depends on HAVE_ARCH_JUMP_LABEL 48 depends on CC_HAS_ASM_GOTO 49 help 50 This option enables a transparent branch optimization that 51 makes certain almost-always-true or almost-always-false branch 52 conditions even cheaper to execute within the kernel. 53 54 Certain performance-sensitive kernel code, such as trace points, 55 scheduler functionality, networking code and KVM have such 56 branches and include support for this optimization technique. 57 58 If it is detected that the compiler has support for "asm goto", 59 the kernel will compile such branches with just a nop 60 instruction. When the condition flag is toggled to true, the 61 nop will be converted to a jump instruction to execute the 62 conditional block of instructions. 63 64 This technique lowers overhead and stress on the branch prediction 65 of the processor and generally makes the kernel faster. The update 66 of the condition is slower, but those are always very rare. 67 68 ( On 32-bit x86, the necessary options added to the compiler 69 flags may increase the size of the kernel slightly. ) 70 71config STATIC_KEYS_SELFTEST 72 bool "Static key selftest" 73 depends on JUMP_LABEL 74 help 75 Boot time self-test of the branch patching code. 76 77config STATIC_CALL_SELFTEST 78 bool "Static call selftest" 79 depends on HAVE_STATIC_CALL 80 help 81 Boot time self-test of the call patching code. 82 83config OPTPROBES 84 def_bool y 85 depends on KPROBES && HAVE_OPTPROBES 86 select TASKS_RCU if PREEMPTION 87 88config KPROBES_ON_FTRACE 89 def_bool y 90 depends on KPROBES && HAVE_KPROBES_ON_FTRACE 91 depends on DYNAMIC_FTRACE_WITH_REGS 92 help 93 If function tracer is enabled and the arch supports full 94 passing of pt_regs to function tracing, then kprobes can 95 optimize on top of function tracing. 96 97config UPROBES 98 def_bool n 99 depends on ARCH_SUPPORTS_UPROBES 100 help 101 Uprobes is the user-space counterpart to kprobes: they 102 enable instrumentation applications (such as 'perf probe') 103 to establish unintrusive probes in user-space binaries and 104 libraries, by executing handler functions when the probes 105 are hit by user-space applications. 106 107 ( These probes come in the form of single-byte breakpoints, 108 managed by the kernel and kept transparent to the probed 109 application. ) 110 111config HAVE_64BIT_ALIGNED_ACCESS 112 def_bool 64BIT && !HAVE_EFFICIENT_UNALIGNED_ACCESS 113 help 114 Some architectures require 64 bit accesses to be 64 bit 115 aligned, which also requires structs containing 64 bit values 116 to be 64 bit aligned too. This includes some 32 bit 117 architectures which can do 64 bit accesses, as well as 64 bit 118 architectures without unaligned access. 119 120 This symbol should be selected by an architecture if 64 bit 121 accesses are required to be 64 bit aligned in this way even 122 though it is not a 64 bit architecture. 123 124 See Documentation/core-api/unaligned-memory-access.rst for 125 more information on the topic of unaligned memory accesses. 126 127config HAVE_EFFICIENT_UNALIGNED_ACCESS 128 bool 129 help 130 Some architectures are unable to perform unaligned accesses 131 without the use of get_unaligned/put_unaligned. Others are 132 unable to perform such accesses efficiently (e.g. trap on 133 unaligned access and require fixing it up in the exception 134 handler.) 135 136 This symbol should be selected by an architecture if it can 137 perform unaligned accesses efficiently to allow different 138 code paths to be selected for these cases. Some network 139 drivers, for example, could opt to not fix up alignment 140 problems with received packets if doing so would not help 141 much. 142 143 See Documentation/core-api/unaligned-memory-access.rst for more 144 information on the topic of unaligned memory accesses. 145 146config ARCH_USE_BUILTIN_BSWAP 147 bool 148 help 149 Modern versions of GCC (since 4.4) have builtin functions 150 for handling byte-swapping. Using these, instead of the old 151 inline assembler that the architecture code provides in the 152 __arch_bswapXX() macros, allows the compiler to see what's 153 happening and offers more opportunity for optimisation. In 154 particular, the compiler will be able to combine the byteswap 155 with a nearby load or store and use load-and-swap or 156 store-and-swap instructions if the architecture has them. It 157 should almost *never* result in code which is worse than the 158 hand-coded assembler in <asm/swab.h>. But just in case it 159 does, the use of the builtins is optional. 160 161 Any architecture with load-and-swap or store-and-swap 162 instructions should set this. And it shouldn't hurt to set it 163 on architectures that don't have such instructions. 164 165config KRETPROBES 166 def_bool y 167 depends on KPROBES && (HAVE_KRETPROBES || HAVE_RETHOOK) 168 169config KRETPROBE_ON_RETHOOK 170 def_bool y 171 depends on HAVE_RETHOOK 172 depends on KRETPROBES 173 select RETHOOK 174 175config USER_RETURN_NOTIFIER 176 bool 177 depends on HAVE_USER_RETURN_NOTIFIER 178 help 179 Provide a kernel-internal notification when a cpu is about to 180 switch to user mode. 181 182config HAVE_IOREMAP_PROT 183 bool 184 185config HAVE_KPROBES 186 bool 187 188config HAVE_KRETPROBES 189 bool 190 191config HAVE_OPTPROBES 192 bool 193 194config HAVE_KPROBES_ON_FTRACE 195 bool 196 197config ARCH_CORRECT_STACKTRACE_ON_KRETPROBE 198 bool 199 help 200 Since kretprobes modifies return address on the stack, the 201 stacktrace may see the kretprobe trampoline address instead 202 of correct one. If the architecture stacktrace code and 203 unwinder can adjust such entries, select this configuration. 204 205config HAVE_FUNCTION_ERROR_INJECTION 206 bool 207 208config HAVE_NMI 209 bool 210 211config HAVE_FUNCTION_DESCRIPTORS 212 bool 213 214config TRACE_IRQFLAGS_SUPPORT 215 bool 216 217# 218# An arch should select this if it provides all these things: 219# 220# task_pt_regs() in asm/processor.h or asm/ptrace.h 221# arch_has_single_step() if there is hardware single-step support 222# arch_has_block_step() if there is hardware block-step support 223# asm/syscall.h supplying asm-generic/syscall.h interface 224# linux/regset.h user_regset interfaces 225# CORE_DUMP_USE_REGSET #define'd in linux/elf.h 226# TIF_SYSCALL_TRACE calls ptrace_report_syscall_{entry,exit} 227# TIF_NOTIFY_RESUME calls resume_user_mode_work() 228# 229config HAVE_ARCH_TRACEHOOK 230 bool 231 232config HAVE_DMA_CONTIGUOUS 233 bool 234 235config GENERIC_SMP_IDLE_THREAD 236 bool 237 238config GENERIC_IDLE_POLL_SETUP 239 bool 240 241config ARCH_HAS_FORTIFY_SOURCE 242 bool 243 help 244 An architecture should select this when it can successfully 245 build and run with CONFIG_FORTIFY_SOURCE. 246 247# 248# Select if the arch provides a historic keepinit alias for the retain_initrd 249# command line option 250# 251config ARCH_HAS_KEEPINITRD 252 bool 253 254# Select if arch has all set_memory_ro/rw/x/nx() functions in asm/cacheflush.h 255config ARCH_HAS_SET_MEMORY 256 bool 257 258# Select if arch has all set_direct_map_invalid/default() functions 259config ARCH_HAS_SET_DIRECT_MAP 260 bool 261 262# 263# Select if the architecture provides the arch_dma_set_uncached symbol to 264# either provide an uncached segment alias for a DMA allocation, or 265# to remap the page tables in place. 266# 267config ARCH_HAS_DMA_SET_UNCACHED 268 bool 269 270# 271# Select if the architectures provides the arch_dma_clear_uncached symbol 272# to undo an in-place page table remap for uncached access. 273# 274config ARCH_HAS_DMA_CLEAR_UNCACHED 275 bool 276 277# Select if arch init_task must go in the __init_task_data section 278config ARCH_TASK_STRUCT_ON_STACK 279 bool 280 281# Select if arch has its private alloc_task_struct() function 282config ARCH_TASK_STRUCT_ALLOCATOR 283 bool 284 285config HAVE_ARCH_THREAD_STRUCT_WHITELIST 286 bool 287 depends on !ARCH_TASK_STRUCT_ALLOCATOR 288 help 289 An architecture should select this to provide hardened usercopy 290 knowledge about what region of the thread_struct should be 291 whitelisted for copying to userspace. Normally this is only the 292 FPU registers. Specifically, arch_thread_struct_whitelist() 293 should be implemented. Without this, the entire thread_struct 294 field in task_struct will be left whitelisted. 295 296# Select if arch has its private alloc_thread_stack() function 297config ARCH_THREAD_STACK_ALLOCATOR 298 bool 299 300# Select if arch wants to size task_struct dynamically via arch_task_struct_size: 301config ARCH_WANTS_DYNAMIC_TASK_STRUCT 302 bool 303 304config ARCH_WANTS_NO_INSTR 305 bool 306 help 307 An architecture should select this if the noinstr macro is being used on 308 functions to denote that the toolchain should avoid instrumenting such 309 functions and is required for correctness. 310 311config ARCH_32BIT_OFF_T 312 bool 313 depends on !64BIT 314 help 315 All new 32-bit architectures should have 64-bit off_t type on 316 userspace side which corresponds to the loff_t kernel type. This 317 is the requirement for modern ABIs. Some existing architectures 318 still support 32-bit off_t. This option is enabled for all such 319 architectures explicitly. 320 321# Selected by 64 bit architectures which have a 32 bit f_tinode in struct ustat 322config ARCH_32BIT_USTAT_F_TINODE 323 bool 324 325config HAVE_ASM_MODVERSIONS 326 bool 327 help 328 This symbol should be selected by an architecture if it provides 329 <asm/asm-prototypes.h> to support the module versioning for symbols 330 exported from assembly code. 331 332config HAVE_REGS_AND_STACK_ACCESS_API 333 bool 334 help 335 This symbol should be selected by an architecture if it supports 336 the API needed to access registers and stack entries from pt_regs, 337 declared in asm/ptrace.h 338 For example the kprobes-based event tracer needs this API. 339 340config HAVE_RSEQ 341 bool 342 depends on HAVE_REGS_AND_STACK_ACCESS_API 343 help 344 This symbol should be selected by an architecture if it 345 supports an implementation of restartable sequences. 346 347config HAVE_FUNCTION_ARG_ACCESS_API 348 bool 349 help 350 This symbol should be selected by an architecture if it supports 351 the API needed to access function arguments from pt_regs, 352 declared in asm/ptrace.h 353 354config HAVE_HW_BREAKPOINT 355 bool 356 depends on PERF_EVENTS 357 358config HAVE_MIXED_BREAKPOINTS_REGS 359 bool 360 depends on HAVE_HW_BREAKPOINT 361 help 362 Depending on the arch implementation of hardware breakpoints, 363 some of them have separate registers for data and instruction 364 breakpoints addresses, others have mixed registers to store 365 them but define the access type in a control register. 366 Select this option if your arch implements breakpoints under the 367 latter fashion. 368 369config HAVE_USER_RETURN_NOTIFIER 370 bool 371 372config HAVE_PERF_EVENTS_NMI 373 bool 374 help 375 System hardware can generate an NMI using the perf event 376 subsystem. Also has support for calculating CPU cycle events 377 to determine how many clock cycles in a given period. 378 379config HAVE_HARDLOCKUP_DETECTOR_PERF 380 bool 381 depends on HAVE_PERF_EVENTS_NMI 382 help 383 The arch chooses to use the generic perf-NMI-based hardlockup 384 detector. Must define HAVE_PERF_EVENTS_NMI. 385 386config HAVE_NMI_WATCHDOG 387 depends on HAVE_NMI 388 bool 389 help 390 The arch provides a low level NMI watchdog. It provides 391 asm/nmi.h, and defines its own arch_touch_nmi_watchdog(). 392 393config HAVE_HARDLOCKUP_DETECTOR_ARCH 394 bool 395 select HAVE_NMI_WATCHDOG 396 help 397 The arch chooses to provide its own hardlockup detector, which is 398 a superset of the HAVE_NMI_WATCHDOG. It also conforms to config 399 interfaces and parameters provided by hardlockup detector subsystem. 400 401config HAVE_PERF_REGS 402 bool 403 help 404 Support selective register dumps for perf events. This includes 405 bit-mapping of each registers and a unique architecture id. 406 407config HAVE_PERF_USER_STACK_DUMP 408 bool 409 help 410 Support user stack dumps for perf event samples. This needs 411 access to the user stack pointer which is not unified across 412 architectures. 413 414config HAVE_ARCH_JUMP_LABEL 415 bool 416 417config HAVE_ARCH_JUMP_LABEL_RELATIVE 418 bool 419 420config MMU_GATHER_TABLE_FREE 421 bool 422 423config MMU_GATHER_RCU_TABLE_FREE 424 bool 425 select MMU_GATHER_TABLE_FREE 426 427config MMU_GATHER_PAGE_SIZE 428 bool 429 430config MMU_GATHER_NO_RANGE 431 bool 432 433config MMU_GATHER_NO_GATHER 434 bool 435 depends on MMU_GATHER_TABLE_FREE 436 437config ARCH_WANT_IRQS_OFF_ACTIVATE_MM 438 bool 439 help 440 Temporary select until all architectures can be converted to have 441 irqs disabled over activate_mm. Architectures that do IPI based TLB 442 shootdowns should enable this. 443 444config ARCH_HAVE_NMI_SAFE_CMPXCHG 445 bool 446 447config HAVE_ALIGNED_STRUCT_PAGE 448 bool 449 help 450 This makes sure that struct pages are double word aligned and that 451 e.g. the SLUB allocator can perform double word atomic operations 452 on a struct page for better performance. However selecting this 453 might increase the size of a struct page by a word. 454 455config HAVE_CMPXCHG_LOCAL 456 bool 457 458config HAVE_CMPXCHG_DOUBLE 459 bool 460 461config ARCH_WEAK_RELEASE_ACQUIRE 462 bool 463 464config ARCH_WANT_IPC_PARSE_VERSION 465 bool 466 467config ARCH_WANT_COMPAT_IPC_PARSE_VERSION 468 bool 469 470config ARCH_WANT_OLD_COMPAT_IPC 471 select ARCH_WANT_COMPAT_IPC_PARSE_VERSION 472 bool 473 474config HAVE_ARCH_SECCOMP 475 bool 476 help 477 An arch should select this symbol to support seccomp mode 1 (the fixed 478 syscall policy), and must provide an overrides for __NR_seccomp_sigreturn, 479 and compat syscalls if the asm-generic/seccomp.h defaults need adjustment: 480 - __NR_seccomp_read_32 481 - __NR_seccomp_write_32 482 - __NR_seccomp_exit_32 483 - __NR_seccomp_sigreturn_32 484 485config HAVE_ARCH_SECCOMP_FILTER 486 bool 487 select HAVE_ARCH_SECCOMP 488 help 489 An arch should select this symbol if it provides all of these things: 490 - all the requirements for HAVE_ARCH_SECCOMP 491 - syscall_get_arch() 492 - syscall_get_arguments() 493 - syscall_rollback() 494 - syscall_set_return_value() 495 - SIGSYS siginfo_t support 496 - secure_computing is called from a ptrace_event()-safe context 497 - secure_computing return value is checked and a return value of -1 498 results in the system call being skipped immediately. 499 - seccomp syscall wired up 500 - if !HAVE_SPARSE_SYSCALL_NR, have SECCOMP_ARCH_NATIVE, 501 SECCOMP_ARCH_NATIVE_NR, SECCOMP_ARCH_NATIVE_NAME defined. If 502 COMPAT is supported, have the SECCOMP_ARCH_COMPAT* defines too. 503 504config SECCOMP 505 prompt "Enable seccomp to safely execute untrusted bytecode" 506 def_bool y 507 depends on HAVE_ARCH_SECCOMP 508 help 509 This kernel feature is useful for number crunching applications 510 that may need to handle untrusted bytecode during their 511 execution. By using pipes or other transports made available 512 to the process as file descriptors supporting the read/write 513 syscalls, it's possible to isolate those applications in their 514 own address space using seccomp. Once seccomp is enabled via 515 prctl(PR_SET_SECCOMP) or the seccomp() syscall, it cannot be 516 disabled and the task is only allowed to execute a few safe 517 syscalls defined by each seccomp mode. 518 519 If unsure, say Y. 520 521config SECCOMP_FILTER 522 def_bool y 523 depends on HAVE_ARCH_SECCOMP_FILTER && SECCOMP && NET 524 help 525 Enable tasks to build secure computing environments defined 526 in terms of Berkeley Packet Filter programs which implement 527 task-defined system call filtering polices. 528 529 See Documentation/userspace-api/seccomp_filter.rst for details. 530 531config SECCOMP_CACHE_DEBUG 532 bool "Show seccomp filter cache status in /proc/pid/seccomp_cache" 533 depends on SECCOMP_FILTER && !HAVE_SPARSE_SYSCALL_NR 534 depends on PROC_FS 535 help 536 This enables the /proc/pid/seccomp_cache interface to monitor 537 seccomp cache data. The file format is subject to change. Reading 538 the file requires CAP_SYS_ADMIN. 539 540 This option is for debugging only. Enabling presents the risk that 541 an adversary may be able to infer the seccomp filter logic. 542 543 If unsure, say N. 544 545config HAVE_ARCH_STACKLEAK 546 bool 547 help 548 An architecture should select this if it has the code which 549 fills the used part of the kernel stack with the STACKLEAK_POISON 550 value before returning from system calls. 551 552config HAVE_STACKPROTECTOR 553 bool 554 help 555 An arch should select this symbol if: 556 - it has implemented a stack canary (e.g. __stack_chk_guard) 557 558config STACKPROTECTOR 559 bool "Stack Protector buffer overflow detection" 560 depends on HAVE_STACKPROTECTOR 561 depends on $(cc-option,-fstack-protector) 562 default y 563 help 564 This option turns on the "stack-protector" GCC feature. This 565 feature puts, at the beginning of functions, a canary value on 566 the stack just before the return address, and validates 567 the value just before actually returning. Stack based buffer 568 overflows (that need to overwrite this return address) now also 569 overwrite the canary, which gets detected and the attack is then 570 neutralized via a kernel panic. 571 572 Functions will have the stack-protector canary logic added if they 573 have an 8-byte or larger character array on the stack. 574 575 This feature requires gcc version 4.2 or above, or a distribution 576 gcc with the feature backported ("-fstack-protector"). 577 578 On an x86 "defconfig" build, this feature adds canary checks to 579 about 3% of all kernel functions, which increases kernel code size 580 by about 0.3%. 581 582config STACKPROTECTOR_STRONG 583 bool "Strong Stack Protector" 584 depends on STACKPROTECTOR 585 depends on $(cc-option,-fstack-protector-strong) 586 default y 587 help 588 Functions will have the stack-protector canary logic added in any 589 of the following conditions: 590 591 - local variable's address used as part of the right hand side of an 592 assignment or function argument 593 - local variable is an array (or union containing an array), 594 regardless of array type or length 595 - uses register local variables 596 597 This feature requires gcc version 4.9 or above, or a distribution 598 gcc with the feature backported ("-fstack-protector-strong"). 599 600 On an x86 "defconfig" build, this feature adds canary checks to 601 about 20% of all kernel functions, which increases the kernel code 602 size by about 2%. 603 604config ARCH_SUPPORTS_SHADOW_CALL_STACK 605 bool 606 help 607 An architecture should select this if it supports the compiler's 608 Shadow Call Stack and implements runtime support for shadow stack 609 switching. 610 611config SHADOW_CALL_STACK 612 bool "Shadow Call Stack" 613 depends on ARCH_SUPPORTS_SHADOW_CALL_STACK 614 depends on DYNAMIC_FTRACE_WITH_REGS || !FUNCTION_GRAPH_TRACER 615 help 616 This option enables the compiler's Shadow Call Stack, which 617 uses a shadow stack to protect function return addresses from 618 being overwritten by an attacker. More information can be found 619 in the compiler's documentation: 620 621 - Clang: https://clang.llvm.org/docs/ShadowCallStack.html 622 - GCC: https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#Instrumentation-Options 623 624 Note that security guarantees in the kernel differ from the 625 ones documented for user space. The kernel must store addresses 626 of shadow stacks in memory, which means an attacker capable of 627 reading and writing arbitrary memory may be able to locate them 628 and hijack control flow by modifying the stacks. 629 630config LTO 631 bool 632 help 633 Selected if the kernel will be built using the compiler's LTO feature. 634 635config LTO_CLANG 636 bool 637 select LTO 638 help 639 Selected if the kernel will be built using Clang's LTO feature. 640 641config ARCH_SUPPORTS_LTO_CLANG 642 bool 643 help 644 An architecture should select this option if it supports: 645 - compiling with Clang, 646 - compiling inline assembly with Clang's integrated assembler, 647 - and linking with LLD. 648 649config ARCH_SUPPORTS_LTO_CLANG_THIN 650 bool 651 help 652 An architecture should select this option if it can support Clang's 653 ThinLTO mode. 654 655config HAS_LTO_CLANG 656 def_bool y 657 depends on CC_IS_CLANG && LD_IS_LLD && AS_IS_LLVM 658 depends on $(success,$(NM) --help | head -n 1 | grep -qi llvm) 659 depends on $(success,$(AR) --help | head -n 1 | grep -qi llvm) 660 depends on ARCH_SUPPORTS_LTO_CLANG 661 depends on !FTRACE_MCOUNT_USE_RECORDMCOUNT 662 depends on !KASAN || KASAN_HW_TAGS 663 depends on !GCOV_KERNEL 664 help 665 The compiler and Kconfig options support building with Clang's 666 LTO. 667 668choice 669 prompt "Link Time Optimization (LTO)" 670 default LTO_NONE 671 help 672 This option enables Link Time Optimization (LTO), which allows the 673 compiler to optimize binaries globally. 674 675 If unsure, select LTO_NONE. Note that LTO is very resource-intensive 676 so it's disabled by default. 677 678config LTO_NONE 679 bool "None" 680 help 681 Build the kernel normally, without Link Time Optimization (LTO). 682 683config LTO_CLANG_FULL 684 bool "Clang Full LTO (EXPERIMENTAL)" 685 depends on HAS_LTO_CLANG 686 depends on !COMPILE_TEST 687 select LTO_CLANG 688 help 689 This option enables Clang's full Link Time Optimization (LTO), which 690 allows the compiler to optimize the kernel globally. If you enable 691 this option, the compiler generates LLVM bitcode instead of ELF 692 object files, and the actual compilation from bitcode happens at 693 the LTO link step, which may take several minutes depending on the 694 kernel configuration. More information can be found from LLVM's 695 documentation: 696 697 https://llvm.org/docs/LinkTimeOptimization.html 698 699 During link time, this option can use a large amount of RAM, and 700 may take much longer than the ThinLTO option. 701 702config LTO_CLANG_THIN 703 bool "Clang ThinLTO (EXPERIMENTAL)" 704 depends on HAS_LTO_CLANG && ARCH_SUPPORTS_LTO_CLANG_THIN 705 select LTO_CLANG 706 help 707 This option enables Clang's ThinLTO, which allows for parallel 708 optimization and faster incremental compiles compared to the 709 CONFIG_LTO_CLANG_FULL option. More information can be found 710 from Clang's documentation: 711 712 https://clang.llvm.org/docs/ThinLTO.html 713 714 If unsure, say Y. 715endchoice 716 717config ARCH_SUPPORTS_CFI_CLANG 718 bool 719 help 720 An architecture should select this option if it can support Clang's 721 Control-Flow Integrity (CFI) checking. 722 723config CFI_CLANG 724 bool "Use Clang's Control Flow Integrity (CFI)" 725 depends on LTO_CLANG && ARCH_SUPPORTS_CFI_CLANG 726 depends on CLANG_VERSION >= 140000 727 select KALLSYMS 728 help 729 This option enables Clang’s forward-edge Control Flow Integrity 730 (CFI) checking, where the compiler injects a runtime check to each 731 indirect function call to ensure the target is a valid function with 732 the correct static type. This restricts possible call targets and 733 makes it more difficult for an attacker to exploit bugs that allow 734 the modification of stored function pointers. More information can be 735 found from Clang's documentation: 736 737 https://clang.llvm.org/docs/ControlFlowIntegrity.html 738 739config CFI_CLANG_SHADOW 740 bool "Use CFI shadow to speed up cross-module checks" 741 default y 742 depends on CFI_CLANG && MODULES 743 help 744 If you select this option, the kernel builds a fast look-up table of 745 CFI check functions in loaded modules to reduce performance overhead. 746 747 If unsure, say Y. 748 749config CFI_PERMISSIVE 750 bool "Use CFI in permissive mode" 751 depends on CFI_CLANG 752 help 753 When selected, Control Flow Integrity (CFI) violations result in a 754 warning instead of a kernel panic. This option should only be used 755 for finding indirect call type mismatches during development. 756 757 If unsure, say N. 758 759config HAVE_ARCH_WITHIN_STACK_FRAMES 760 bool 761 help 762 An architecture should select this if it can walk the kernel stack 763 frames to determine if an object is part of either the arguments 764 or local variables (i.e. that it excludes saved return addresses, 765 and similar) by implementing an inline arch_within_stack_frames(), 766 which is used by CONFIG_HARDENED_USERCOPY. 767 768config HAVE_CONTEXT_TRACKING 769 bool 770 help 771 Provide kernel/user boundaries probes necessary for subsystems 772 that need it, such as userspace RCU extended quiescent state. 773 Syscalls need to be wrapped inside user_exit()-user_enter(), either 774 optimized behind static key or through the slow path using TIF_NOHZ 775 flag. Exceptions handlers must be wrapped as well. Irqs are already 776 protected inside rcu_irq_enter/rcu_irq_exit() but preemption or signal 777 handling on irq exit still need to be protected. 778 779config HAVE_CONTEXT_TRACKING_OFFSTACK 780 bool 781 help 782 Architecture neither relies on exception_enter()/exception_exit() 783 nor on schedule_user(). Also preempt_schedule_notrace() and 784 preempt_schedule_irq() can't be called in a preemptible section 785 while context tracking is CONTEXT_USER. This feature reflects a sane 786 entry implementation where the following requirements are met on 787 critical entry code, ie: before user_exit() or after user_enter(): 788 789 - Critical entry code isn't preemptible (or better yet: 790 not interruptible). 791 - No use of RCU read side critical sections, unless rcu_nmi_enter() 792 got called. 793 - No use of instrumentation, unless instrumentation_begin() got 794 called. 795 796config HAVE_TIF_NOHZ 797 bool 798 help 799 Arch relies on TIF_NOHZ and syscall slow path to implement context 800 tracking calls to user_enter()/user_exit(). 801 802config HAVE_VIRT_CPU_ACCOUNTING 803 bool 804 805config HAVE_VIRT_CPU_ACCOUNTING_IDLE 806 bool 807 help 808 Architecture has its own way to account idle CPU time and therefore 809 doesn't implement vtime_account_idle(). 810 811config ARCH_HAS_SCALED_CPUTIME 812 bool 813 814config HAVE_VIRT_CPU_ACCOUNTING_GEN 815 bool 816 default y if 64BIT 817 help 818 With VIRT_CPU_ACCOUNTING_GEN, cputime_t becomes 64-bit. 819 Before enabling this option, arch code must be audited 820 to ensure there are no races in concurrent read/write of 821 cputime_t. For example, reading/writing 64-bit cputime_t on 822 some 32-bit arches may require multiple accesses, so proper 823 locking is needed to protect against concurrent accesses. 824 825config HAVE_IRQ_TIME_ACCOUNTING 826 bool 827 help 828 Archs need to ensure they use a high enough resolution clock to 829 support irq time accounting and then call enable_sched_clock_irqtime(). 830 831config HAVE_MOVE_PUD 832 bool 833 help 834 Architectures that select this are able to move page tables at the 835 PUD level. If there are only 3 page table levels, the move effectively 836 happens at the PGD level. 837 838config HAVE_MOVE_PMD 839 bool 840 help 841 Archs that select this are able to move page tables at the PMD level. 842 843config HAVE_ARCH_TRANSPARENT_HUGEPAGE 844 bool 845 846config HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD 847 bool 848 849config HAVE_ARCH_HUGE_VMAP 850 bool 851 852# 853# Archs that select this would be capable of PMD-sized vmaps (i.e., 854# arch_vmap_pmd_supported() returns true), and they must make no assumptions 855# that vmalloc memory is mapped with PAGE_SIZE ptes. The VM_NO_HUGE_VMAP flag 856# can be used to prohibit arch-specific allocations from using hugepages to 857# help with this (e.g., modules may require it). 858# 859config HAVE_ARCH_HUGE_VMALLOC 860 depends on HAVE_ARCH_HUGE_VMAP 861 bool 862 863config ARCH_WANT_HUGE_PMD_SHARE 864 bool 865 866config HAVE_ARCH_SOFT_DIRTY 867 bool 868 869config HAVE_MOD_ARCH_SPECIFIC 870 bool 871 help 872 The arch uses struct mod_arch_specific to store data. Many arches 873 just need a simple module loader without arch specific data - those 874 should not enable this. 875 876config MODULES_USE_ELF_RELA 877 bool 878 help 879 Modules only use ELF RELA relocations. Modules with ELF REL 880 relocations will give an error. 881 882config MODULES_USE_ELF_REL 883 bool 884 help 885 Modules only use ELF REL relocations. Modules with ELF RELA 886 relocations will give an error. 887 888config HAVE_IRQ_EXIT_ON_IRQ_STACK 889 bool 890 help 891 Architecture doesn't only execute the irq handler on the irq stack 892 but also irq_exit(). This way we can process softirqs on this irq 893 stack instead of switching to a new one when we call __do_softirq() 894 in the end of an hardirq. 895 This spares a stack switch and improves cache usage on softirq 896 processing. 897 898config HAVE_SOFTIRQ_ON_OWN_STACK 899 bool 900 help 901 Architecture provides a function to run __do_softirq() on a 902 separate stack. 903 904config ALTERNATE_USER_ADDRESS_SPACE 905 bool 906 help 907 Architectures set this when the CPU uses separate address 908 spaces for kernel and user space pointers. In this case, the 909 access_ok() check on a __user pointer is skipped. 910 911config PGTABLE_LEVELS 912 int 913 default 2 914 915config ARCH_HAS_ELF_RANDOMIZE 916 bool 917 help 918 An architecture supports choosing randomized locations for 919 stack, mmap, brk, and ET_DYN. Defined functions: 920 - arch_mmap_rnd() 921 - arch_randomize_brk() 922 923config HAVE_ARCH_MMAP_RND_BITS 924 bool 925 help 926 An arch should select this symbol if it supports setting a variable 927 number of bits for use in establishing the base address for mmap 928 allocations, has MMU enabled and provides values for both: 929 - ARCH_MMAP_RND_BITS_MIN 930 - ARCH_MMAP_RND_BITS_MAX 931 932config HAVE_EXIT_THREAD 933 bool 934 help 935 An architecture implements exit_thread. 936 937config ARCH_MMAP_RND_BITS_MIN 938 int 939 940config ARCH_MMAP_RND_BITS_MAX 941 int 942 943config ARCH_MMAP_RND_BITS_DEFAULT 944 int 945 946config ARCH_MMAP_RND_BITS 947 int "Number of bits to use for ASLR of mmap base address" if EXPERT 948 range ARCH_MMAP_RND_BITS_MIN ARCH_MMAP_RND_BITS_MAX 949 default ARCH_MMAP_RND_BITS_DEFAULT if ARCH_MMAP_RND_BITS_DEFAULT 950 default ARCH_MMAP_RND_BITS_MIN 951 depends on HAVE_ARCH_MMAP_RND_BITS 952 help 953 This value can be used to select the number of bits to use to 954 determine the random offset to the base address of vma regions 955 resulting from mmap allocations. This value will be bounded 956 by the architecture's minimum and maximum supported values. 957 958 This value can be changed after boot using the 959 /proc/sys/vm/mmap_rnd_bits tunable 960 961config HAVE_ARCH_MMAP_RND_COMPAT_BITS 962 bool 963 help 964 An arch should select this symbol if it supports running applications 965 in compatibility mode, supports setting a variable number of bits for 966 use in establishing the base address for mmap allocations, has MMU 967 enabled and provides values for both: 968 - ARCH_MMAP_RND_COMPAT_BITS_MIN 969 - ARCH_MMAP_RND_COMPAT_BITS_MAX 970 971config ARCH_MMAP_RND_COMPAT_BITS_MIN 972 int 973 974config ARCH_MMAP_RND_COMPAT_BITS_MAX 975 int 976 977config ARCH_MMAP_RND_COMPAT_BITS_DEFAULT 978 int 979 980config ARCH_MMAP_RND_COMPAT_BITS 981 int "Number of bits to use for ASLR of mmap base address for compatible applications" if EXPERT 982 range ARCH_MMAP_RND_COMPAT_BITS_MIN ARCH_MMAP_RND_COMPAT_BITS_MAX 983 default ARCH_MMAP_RND_COMPAT_BITS_DEFAULT if ARCH_MMAP_RND_COMPAT_BITS_DEFAULT 984 default ARCH_MMAP_RND_COMPAT_BITS_MIN 985 depends on HAVE_ARCH_MMAP_RND_COMPAT_BITS 986 help 987 This value can be used to select the number of bits to use to 988 determine the random offset to the base address of vma regions 989 resulting from mmap allocations for compatible applications This 990 value will be bounded by the architecture's minimum and maximum 991 supported values. 992 993 This value can be changed after boot using the 994 /proc/sys/vm/mmap_rnd_compat_bits tunable 995 996config HAVE_ARCH_COMPAT_MMAP_BASES 997 bool 998 help 999 This allows 64bit applications to invoke 32-bit mmap() syscall 1000 and vice-versa 32-bit applications to call 64-bit mmap(). 1001 Required for applications doing different bitness syscalls. 1002 1003config PAGE_SIZE_LESS_THAN_64KB 1004 def_bool y 1005 depends on !ARM64_64K_PAGES 1006 depends on !IA64_PAGE_SIZE_64KB 1007 depends on !PAGE_SIZE_64KB 1008 depends on !PARISC_PAGE_SIZE_64KB 1009 depends on !PPC_64K_PAGES 1010 depends on PAGE_SIZE_LESS_THAN_256KB 1011 1012config PAGE_SIZE_LESS_THAN_256KB 1013 def_bool y 1014 depends on !PPC_256K_PAGES 1015 depends on !PAGE_SIZE_256KB 1016 1017# This allows to use a set of generic functions to determine mmap base 1018# address by giving priority to top-down scheme only if the process 1019# is not in legacy mode (compat task, unlimited stack size or 1020# sysctl_legacy_va_layout). 1021# Architecture that selects this option can provide its own version of: 1022# - STACK_RND_MASK 1023config ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT 1024 bool 1025 depends on MMU 1026 select ARCH_HAS_ELF_RANDOMIZE 1027 1028config HAVE_STACK_VALIDATION 1029 bool 1030 help 1031 Architecture supports the 'objtool check' host tool command, which 1032 performs compile-time stack metadata validation. 1033 1034config HAVE_RELIABLE_STACKTRACE 1035 bool 1036 help 1037 Architecture has either save_stack_trace_tsk_reliable() or 1038 arch_stack_walk_reliable() function which only returns a stack trace 1039 if it can guarantee the trace is reliable. 1040 1041config HAVE_ARCH_HASH 1042 bool 1043 default n 1044 help 1045 If this is set, the architecture provides an <asm/hash.h> 1046 file which provides platform-specific implementations of some 1047 functions in <linux/hash.h> or fs/namei.c. 1048 1049config HAVE_ARCH_NVRAM_OPS 1050 bool 1051 1052config ISA_BUS_API 1053 def_bool ISA 1054 1055# 1056# ABI hall of shame 1057# 1058config CLONE_BACKWARDS 1059 bool 1060 help 1061 Architecture has tls passed as the 4th argument of clone(2), 1062 not the 5th one. 1063 1064config CLONE_BACKWARDS2 1065 bool 1066 help 1067 Architecture has the first two arguments of clone(2) swapped. 1068 1069config CLONE_BACKWARDS3 1070 bool 1071 help 1072 Architecture has tls passed as the 3rd argument of clone(2), 1073 not the 5th one. 1074 1075config ODD_RT_SIGACTION 1076 bool 1077 help 1078 Architecture has unusual rt_sigaction(2) arguments 1079 1080config OLD_SIGSUSPEND 1081 bool 1082 help 1083 Architecture has old sigsuspend(2) syscall, of one-argument variety 1084 1085config OLD_SIGSUSPEND3 1086 bool 1087 help 1088 Even weirder antique ABI - three-argument sigsuspend(2) 1089 1090config OLD_SIGACTION 1091 bool 1092 help 1093 Architecture has old sigaction(2) syscall. Nope, not the same 1094 as OLD_SIGSUSPEND | OLD_SIGSUSPEND3 - alpha has sigsuspend(2), 1095 but fairly different variant of sigaction(2), thanks to OSF/1 1096 compatibility... 1097 1098config COMPAT_OLD_SIGACTION 1099 bool 1100 1101config COMPAT_32BIT_TIME 1102 bool "Provide system calls for 32-bit time_t" 1103 default !64BIT || COMPAT 1104 help 1105 This enables 32 bit time_t support in addition to 64 bit time_t support. 1106 This is relevant on all 32-bit architectures, and 64-bit architectures 1107 as part of compat syscall handling. 1108 1109config ARCH_NO_PREEMPT 1110 bool 1111 1112config ARCH_EPHEMERAL_INODES 1113 def_bool n 1114 help 1115 An arch should select this symbol if it doesn't keep track of inode 1116 instances on its own, but instead relies on something else (e.g. the 1117 host kernel for an UML kernel). 1118 1119config ARCH_SUPPORTS_RT 1120 bool 1121 1122config CPU_NO_EFFICIENT_FFS 1123 def_bool n 1124 1125config HAVE_ARCH_VMAP_STACK 1126 def_bool n 1127 help 1128 An arch should select this symbol if it can support kernel stacks 1129 in vmalloc space. This means: 1130 1131 - vmalloc space must be large enough to hold many kernel stacks. 1132 This may rule out many 32-bit architectures. 1133 1134 - Stacks in vmalloc space need to work reliably. For example, if 1135 vmap page tables are created on demand, either this mechanism 1136 needs to work while the stack points to a virtual address with 1137 unpopulated page tables or arch code (switch_to() and switch_mm(), 1138 most likely) needs to ensure that the stack's page table entries 1139 are populated before running on a possibly unpopulated stack. 1140 1141 - If the stack overflows into a guard page, something reasonable 1142 should happen. The definition of "reasonable" is flexible, but 1143 instantly rebooting without logging anything would be unfriendly. 1144 1145config VMAP_STACK 1146 default y 1147 bool "Use a virtually-mapped stack" 1148 depends on HAVE_ARCH_VMAP_STACK 1149 depends on !KASAN || KASAN_HW_TAGS || KASAN_VMALLOC 1150 help 1151 Enable this if you want the use virtually-mapped kernel stacks 1152 with guard pages. This causes kernel stack overflows to be 1153 caught immediately rather than causing difficult-to-diagnose 1154 corruption. 1155 1156 To use this with software KASAN modes, the architecture must support 1157 backing virtual mappings with real shadow memory, and KASAN_VMALLOC 1158 must be enabled. 1159 1160config HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET 1161 def_bool n 1162 help 1163 An arch should select this symbol if it can support kernel stack 1164 offset randomization with calls to add_random_kstack_offset() 1165 during syscall entry and choose_random_kstack_offset() during 1166 syscall exit. Careful removal of -fstack-protector-strong and 1167 -fstack-protector should also be applied to the entry code and 1168 closely examined, as the artificial stack bump looks like an array 1169 to the compiler, so it will attempt to add canary checks regardless 1170 of the static branch state. 1171 1172config RANDOMIZE_KSTACK_OFFSET 1173 bool "Support for randomizing kernel stack offset on syscall entry" if EXPERT 1174 default y 1175 depends on HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET 1176 depends on INIT_STACK_NONE || !CC_IS_CLANG || CLANG_VERSION >= 140000 1177 help 1178 The kernel stack offset can be randomized (after pt_regs) by 1179 roughly 5 bits of entropy, frustrating memory corruption 1180 attacks that depend on stack address determinism or 1181 cross-syscall address exposures. 1182 1183 The feature is controlled via the "randomize_kstack_offset=on/off" 1184 kernel boot param, and if turned off has zero overhead due to its use 1185 of static branches (see JUMP_LABEL). 1186 1187 If unsure, say Y. 1188 1189config RANDOMIZE_KSTACK_OFFSET_DEFAULT 1190 bool "Default state of kernel stack offset randomization" 1191 depends on RANDOMIZE_KSTACK_OFFSET 1192 help 1193 Kernel stack offset randomization is controlled by kernel boot param 1194 "randomize_kstack_offset=on/off", and this config chooses the default 1195 boot state. 1196 1197config ARCH_OPTIONAL_KERNEL_RWX 1198 def_bool n 1199 1200config ARCH_OPTIONAL_KERNEL_RWX_DEFAULT 1201 def_bool n 1202 1203config ARCH_HAS_STRICT_KERNEL_RWX 1204 def_bool n 1205 1206config STRICT_KERNEL_RWX 1207 bool "Make kernel text and rodata read-only" if ARCH_OPTIONAL_KERNEL_RWX 1208 depends on ARCH_HAS_STRICT_KERNEL_RWX 1209 default !ARCH_OPTIONAL_KERNEL_RWX || ARCH_OPTIONAL_KERNEL_RWX_DEFAULT 1210 help 1211 If this is set, kernel text and rodata memory will be made read-only, 1212 and non-text memory will be made non-executable. This provides 1213 protection against certain security exploits (e.g. executing the heap 1214 or modifying text) 1215 1216 These features are considered standard security practice these days. 1217 You should say Y here in almost all cases. 1218 1219config ARCH_HAS_STRICT_MODULE_RWX 1220 def_bool n 1221 1222config STRICT_MODULE_RWX 1223 bool "Set loadable kernel module data as NX and text as RO" if ARCH_OPTIONAL_KERNEL_RWX 1224 depends on ARCH_HAS_STRICT_MODULE_RWX && MODULES 1225 default !ARCH_OPTIONAL_KERNEL_RWX || ARCH_OPTIONAL_KERNEL_RWX_DEFAULT 1226 help 1227 If this is set, module text and rodata memory will be made read-only, 1228 and non-text memory will be made non-executable. This provides 1229 protection against certain security exploits (e.g. writing to text) 1230 1231# select if the architecture provides an asm/dma-direct.h header 1232config ARCH_HAS_PHYS_TO_DMA 1233 bool 1234 1235config HAVE_ARCH_COMPILER_H 1236 bool 1237 help 1238 An architecture can select this if it provides an 1239 asm/compiler.h header that should be included after 1240 linux/compiler-*.h in order to override macro definitions that those 1241 headers generally provide. 1242 1243config HAVE_ARCH_PREL32_RELOCATIONS 1244 bool 1245 help 1246 May be selected by an architecture if it supports place-relative 1247 32-bit relocations, both in the toolchain and in the module loader, 1248 in which case relative references can be used in special sections 1249 for PCI fixup, initcalls etc which are only half the size on 64 bit 1250 architectures, and don't require runtime relocation on relocatable 1251 kernels. 1252 1253config ARCH_USE_MEMREMAP_PROT 1254 bool 1255 1256config LOCK_EVENT_COUNTS 1257 bool "Locking event counts collection" 1258 depends on DEBUG_FS 1259 help 1260 Enable light-weight counting of various locking related events 1261 in the system with minimal performance impact. This reduces 1262 the chance of application behavior change because of timing 1263 differences. The counts are reported via debugfs. 1264 1265# Select if the architecture has support for applying RELR relocations. 1266config ARCH_HAS_RELR 1267 bool 1268 1269config RELR 1270 bool "Use RELR relocation packing" 1271 depends on ARCH_HAS_RELR && TOOLS_SUPPORT_RELR 1272 default y 1273 help 1274 Store the kernel's dynamic relocations in the RELR relocation packing 1275 format. Requires a compatible linker (LLD supports this feature), as 1276 well as compatible NM and OBJCOPY utilities (llvm-nm and llvm-objcopy 1277 are compatible). 1278 1279config ARCH_HAS_MEM_ENCRYPT 1280 bool 1281 1282config ARCH_HAS_CC_PLATFORM 1283 bool 1284 1285config HAVE_SPARSE_SYSCALL_NR 1286 bool 1287 help 1288 An architecture should select this if its syscall numbering is sparse 1289 to save space. For example, MIPS architecture has a syscall array with 1290 entries at 4000, 5000 and 6000 locations. This option turns on syscall 1291 related optimizations for a given architecture. 1292 1293config ARCH_HAS_VDSO_DATA 1294 bool 1295 1296config HAVE_STATIC_CALL 1297 bool 1298 1299config HAVE_STATIC_CALL_INLINE 1300 bool 1301 depends on HAVE_STATIC_CALL 1302 1303config HAVE_PREEMPT_DYNAMIC 1304 bool 1305 1306config HAVE_PREEMPT_DYNAMIC_CALL 1307 bool 1308 depends on HAVE_STATIC_CALL 1309 select HAVE_PREEMPT_DYNAMIC 1310 help 1311 An architecture should select this if it can handle the preemption 1312 model being selected at boot time using static calls. 1313 1314 Where an architecture selects HAVE_STATIC_CALL_INLINE, any call to a 1315 preemption function will be patched directly. 1316 1317 Where an architecture does not select HAVE_STATIC_CALL_INLINE, any 1318 call to a preemption function will go through a trampoline, and the 1319 trampoline will be patched. 1320 1321 It is strongly advised to support inline static call to avoid any 1322 overhead. 1323 1324config HAVE_PREEMPT_DYNAMIC_KEY 1325 bool 1326 depends on HAVE_ARCH_JUMP_LABEL && CC_HAS_ASM_GOTO 1327 select HAVE_PREEMPT_DYNAMIC 1328 help 1329 An architecture should select this if it can handle the preemption 1330 model being selected at boot time using static keys. 1331 1332 Each preemption function will be given an early return based on a 1333 static key. This should have slightly lower overhead than non-inline 1334 static calls, as this effectively inlines each trampoline into the 1335 start of its callee. This may avoid redundant work, and may 1336 integrate better with CFI schemes. 1337 1338 This will have greater overhead than using inline static calls as 1339 the call to the preemption function cannot be entirely elided. 1340 1341config ARCH_WANT_LD_ORPHAN_WARN 1342 bool 1343 help 1344 An arch should select this symbol once all linker sections are explicitly 1345 included, size-asserted, or discarded in the linker scripts. This is 1346 important because we never want expected sections to be placed heuristically 1347 by the linker, since the locations of such sections can change between linker 1348 versions. 1349 1350config HAVE_ARCH_PFN_VALID 1351 bool 1352 1353config ARCH_SUPPORTS_DEBUG_PAGEALLOC 1354 bool 1355 1356config ARCH_SUPPORTS_PAGE_TABLE_CHECK 1357 bool 1358 1359config ARCH_SPLIT_ARG64 1360 bool 1361 help 1362 If a 32-bit architecture requires 64-bit arguments to be split into 1363 pairs of 32-bit arguments, select this option. 1364 1365config ARCH_HAS_ELFCORE_COMPAT 1366 bool 1367 1368config ARCH_HAS_PARANOID_L1D_FLUSH 1369 bool 1370 1371config DYNAMIC_SIGFRAME 1372 bool 1373 1374# Select, if arch has a named attribute group bound to NUMA device nodes. 1375config HAVE_ARCH_NODE_DEV_GROUP 1376 bool 1377 1378source "kernel/gcov/Kconfig" 1379 1380source "scripts/gcc-plugins/Kconfig" 1381 1382endmenu 1383