CONFIG_STACKPROTECTOR_PER_TASK: Use a unique stack canary value for each task

General informations

The Linux kernel configuration item CONFIG_STACKPROTECTOR_PER_TASK has multiple definitions:

Use a unique stack canary value for each task found in arch/arm/Kconfig

The configuration item CONFIG_STACKPROTECTOR_PER_TASK:

• prompt: Use a unique stack canary value for each task
• type: bool
• depends on: ( CONFIG_STACKPROTECTOR && CONFIG_CURRENT_POINTER_IN_TPIDRURO && ! CONFIG_XIP_DEFLATED_DATA ) && ( CONFIG_GCC_PLUGINS || CONFIG_CC_HAVE_STACKPROTECTOR_TLS )
• defined in arch/arm/Kconfig
• found in Linux kernels: 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

Due to the fact that GCC uses an ordinary symbol reference from which to load the value of the stack canary, this value can only change at reboot time on SMP systems, and all tasks running in the kernel's address space are forced to use the same canary value for the entire duration that the system is up.

Enable this option to switch to a different method that uses a different canary value for each task.

found in arch/riscv/Kconfig

The configuration item CONFIG_STACKPROTECTOR_PER_TASK:

• prompt:
• type: bool
• depends on: (! CONFIG_RANDSTRUCT ) && ( CONFIG_STACKPROTECTOR && CONFIG_CC_HAVE_STACKPROTECTOR_TLS )
• defined in arch/riscv/Kconfig
• found in Linux kernels: 5.12–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

(none)

found in arch/arm64/Kconfig

The configuration item CONFIG_STACKPROTECTOR_PER_TASK:

• prompt:
• type: bool
• depends on: CONFIG_STACKPROTECTOR && CONFIG_CC_HAVE_STACKPROTECTOR_SYSREG
• defined in arch/arm64/Kconfig
• found in Linux kernels: 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

(none)

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: