CONFIG_STRICT_DEVMEM: Filter access to /dev/mem

General informations

The Linux kernel configuration item CONFIG_STRICT_DEVMEM has multiple definitions:

Filter access to /dev/mem found in lib/Kconfig.debug

The configuration item CONFIG_STRICT_DEVMEM:

• prompt: Filter access to /dev/mem
• type: bool
• depends on: ( CONFIG_MMU && CONFIG_DEVMEM ) && ( CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED || CONFIG_GENERIC_LIB_DEVMEM_IS_ALLOWED ) && ( CONFIG_PPC || CONFIG_X86 || CONFIG_ARM64 )
• defined in lib/Kconfig.debug
• found in Linux kernels: 4.5–4.20, 5.0–5.19, 6.0–6.12

Help text

If this option is disabled, you allow userspace (root) access to all of memory, including kernel and userspace memory. Accidental access to this is obviously disastrous, but specific access can be used by people debugging the kernel. Note that with PAT support enabled, even in this case there are restrictions on /dev/mem use due to the cache aliasing requirements.

If this option is switched on, and IO_STRICT_DEVMEM=n, the /dev/mem file only allows userspace access to PCI space and the BIOS code and data regions. This is sufficient for dosemu and X and all common users of /dev/mem.

If in doubt, say Y.

Filter access to /dev/mem found in arch/x86/Kconfig.debug

The configuration item CONFIG_STRICT_DEVMEM:

• prompt: Filter access to /dev/mem
• type: bool
• depends on: (none)
• defined in arch/x86/Kconfig.debug
• found in Linux kernels: 2.6.27–2.6.39, 3.0–3.19, 4.0–4.4

Help text

If this option is disabled, you allow userspace (root) access to all of memory, including kernel and userspace memory. Accidental access to this is obviously disastrous, but specific access can be used by people debugging the kernel. Note that with PAT support enabled, even in this case there are restrictions on /dev/mem use due to the cache aliasing requirements.

If this option is switched on, the /dev/mem file only allows userspace access to PCI space and the BIOS code and data regions. This is sufficient for dosemu and X and all common users of /dev/mem.

If in doubt, say Y.

Filter access to /dev/mem found in arch/unicore32/Kconfig.debug

The configuration item CONFIG_STRICT_DEVMEM:

• prompt: Filter access to /dev/mem
• type: bool
• depends on: CONFIG_MMU
• defined in arch/unicore32/Kconfig.debug
• found in Linux kernels: 2.6.39, 3.0–3.19, 4.0–4.4

Help text

If this option is disabled, you allow userspace (root) access to all of memory, including kernel and userspace memory. Accidental access to this is obviously disastrous, but specific access can be used by people debugging the kernel.

If this option is switched on, the /dev/mem file only allows userspace access to memory mapped peripherals.

If in doubt, say Y.

Filter access to /dev/mem found in arch/s390/Kconfig.debug

The configuration item CONFIG_STRICT_DEVMEM:

• prompt: Filter access to /dev/mem
• type: bool
• depends on: (none)
• defined in arch/s390/Kconfig.debug
• found in Linux kernels: 2.6.37–2.6.39, 3.0–3.19, 4.0–4.4

Help text

This option restricts access to /dev/mem. If this option is disabled, you allow userspace access to all memory, including kernel and userspace memory. Accidental memory access is likely to be disastrous. Memory access is required for experts who want to debug the kernel.

If you are unsure, say Y.

Filter access to /dev/mem found in arch/powerpc/Kconfig.debug

The configuration item CONFIG_STRICT_DEVMEM:

• prompt: Filter access to /dev/mem
• type: bool
• depends on: (none)
• defined in arch/powerpc/Kconfig.debug
• found in Linux kernels: 3.3–3.19, 4.0–4.4

Help text

This option restricts access to /dev/mem. If this option is disabled, you allow userspace access to all memory, including kernel and userspace memory. Accidental memory access is likely to be disastrous. Memory access is required for experts who want to debug the kernel.

If you are unsure, say Y.

Filter access to /dev/mem found in arch/arm64/Kconfig.debug

The configuration item CONFIG_STRICT_DEVMEM:

• prompt: Filter access to /dev/mem
• type: bool
• depends on: CONFIG_MMU
• defined in arch/arm64/Kconfig.debug
• found in Linux kernels: 3.15–3.19, 4.0–4.4

Help text

If this option is disabled, you allow userspace (root) access to all of memory, including kernel and userspace memory. Accidental access to this is obviously disastrous, but specific access can be used by people debugging the kernel.

If this option is switched on, the /dev/mem file only allows userspace access to memory mapped peripherals.

If in doubt, say Y.

Filter access to /dev/mem found in arch/arm/Kconfig.debug

The configuration item CONFIG_STRICT_DEVMEM:

• prompt: Filter access to /dev/mem
• type: bool
• depends on: CONFIG_MMU
• defined in arch/arm/Kconfig.debug
• found in Linux kernels: 2.6.37–2.6.39, 3.0–3.19, 4.0–4.4

Help text

If this option is disabled, you allow userspace (root) access to all of memory, including kernel and userspace memory. Accidental access to this is obviously disastrous, but specific access can be used by people debugging the kernel.

If this option is switched on, the /dev/mem file only allows userspace access to memory mapped peripherals.

If in doubt, say Y.

found in arch/tile/Kconfig

The configuration item CONFIG_STRICT_DEVMEM:

• prompt:
• type: bool
• depends on: (none)
• defined in arch/tile/Kconfig
• found in Linux kernels: 2.6.36–2.6.39, 3.0–3.19, 4.0–4.4

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: