2012-04-20 13:45:54 +00:00
|
|
|
menu "Kernel hacking"
|
|
|
|
|
|
|
|
source "lib/Kconfig.debug"
|
|
|
|
|
2016-10-27 16:27:31 +00:00
|
|
|
config ARM64_PTDUMP_CORE
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
config ARM64_PTDUMP_DEBUGFS
|
2014-11-26 00:28:39 +00:00
|
|
|
bool "Export kernel pagetable layout to userspace via debugfs"
|
|
|
|
depends on DEBUG_KERNEL
|
2016-10-27 16:27:31 +00:00
|
|
|
select ARM64_PTDUMP_CORE
|
2014-11-26 00:28:39 +00:00
|
|
|
select DEBUG_FS
|
|
|
|
help
|
|
|
|
Say Y here if you want to show the kernel pagetable layout in a
|
|
|
|
debugfs file. This information is only useful for kernel developers
|
|
|
|
who are working in architecture specific areas of the kernel.
|
|
|
|
It is probably not a good idea to enable this feature in a production
|
|
|
|
kernel.
|
arm64: enable CONFIG_SET_MODULE_RONX by default
The SET_MODULE_RONX protections are effectively the same as the
DEBUG_RODATA protections we enabled by default back in commit
57efac2f7108e325 ("arm64: enable CONFIG_DEBUG_RODATA by default"). It
seems unusual to have one but not the other.
As evidenced by the help text, the rationale appears to be that
SET_MODULE_RONX interacts poorly with tracing and patching, but both of
these make use of the insn framework, which takes SET_MODULE_RONX into
account. Any remaining issues are bugs which should be fixed regardless
of the default state of the option.
This patch enables DEBUG_SET_MODULE_RONX by default, and replaces the
help text with a new wording derived from the DEBUG_RODATA help text,
which better describes the functionality. Previously, the DEBUG_RODATA
entry was inconsistently indented with spaces, which are replaced with
tabs as with the other Kconfig entries.
Additionally, the wording of recommended defaults is made consistent for
all options. These are placed in a new paragraph, unquoted, as a full
sentence (with a period/full stop) as this appears to be the most common
form per $(git grep 'in doubt').
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Acked-by: Kees Cook <keescook@chromium.org>
Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2016-05-13 11:20:36 +00:00
|
|
|
|
|
|
|
If in doubt, say N.
|
2014-11-26 00:28:39 +00:00
|
|
|
|
2013-01-17 12:31:45 +00:00
|
|
|
config PID_IN_CONTEXTIDR
|
|
|
|
bool "Write the current PID to the CONTEXTIDR register"
|
|
|
|
help
|
|
|
|
Enabling this option causes the kernel to write the current PID to
|
|
|
|
the CONTEXTIDR register, at the expense of some additional
|
|
|
|
instructions during context switch. Say Y here only if you are
|
|
|
|
planning to use hardware trace tools with this kernel.
|
|
|
|
|
2014-06-24 15:51:37 +00:00
|
|
|
config ARM64_RANDOMIZE_TEXT_OFFSET
|
|
|
|
bool "Randomize TEXT_OFFSET at build time"
|
|
|
|
help
|
|
|
|
Say Y here if you want the image load offset (AKA TEXT_OFFSET)
|
|
|
|
of the kernel to be randomized at build-time. When selected,
|
|
|
|
this option will cause TEXT_OFFSET to be randomized upon any
|
|
|
|
build of the kernel, and the offset will be reflected in the
|
|
|
|
text_offset field of the resulting Image. This can be used to
|
|
|
|
fuzz-test bootloaders which respect text_offset.
|
|
|
|
|
|
|
|
This option is intended for bootloader and/or kernel testing
|
|
|
|
only. Bootloaders must make no assumptions regarding the value
|
|
|
|
of TEXT_OFFSET and platforms must not require a specific
|
|
|
|
value.
|
|
|
|
|
2016-10-27 16:27:34 +00:00
|
|
|
config DEBUG_WX
|
|
|
|
bool "Warn on W+X mappings at boot"
|
|
|
|
select ARM64_PTDUMP_CORE
|
|
|
|
---help---
|
|
|
|
Generate a warning if any W+X mappings are found at boot.
|
|
|
|
|
|
|
|
This is useful for discovering cases where the kernel is leaving
|
|
|
|
W+X mappings after applying NX, as such mappings are a security risk.
|
|
|
|
This check also includes UXN, which should be set on all kernel
|
|
|
|
mappings.
|
|
|
|
|
|
|
|
Look for a message in dmesg output like this:
|
|
|
|
|
|
|
|
arm64/mm: Checked W+X mappings: passed, no W+X pages found.
|
|
|
|
|
|
|
|
or like this, if the check failed:
|
|
|
|
|
|
|
|
arm64/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
|
|
|
|
|
|
|
|
Note that even if the check fails, your kernel is possibly
|
|
|
|
still fine, as W+X mappings are not a security hole in
|
|
|
|
themselves, what they do is that they make the exploitation
|
|
|
|
of other unfixed kernel bugs easier.
|
|
|
|
|
|
|
|
There is no runtime or memory usage effect of this option
|
|
|
|
once the kernel has booted up - it's a one time check.
|
|
|
|
|
|
|
|
If in doubt, say "Y".
|
|
|
|
|
2015-01-22 01:36:06 +00:00
|
|
|
config DEBUG_ALIGN_RODATA
|
2017-02-07 00:31:58 +00:00
|
|
|
depends on STRICT_KERNEL_RWX
|
2015-01-22 01:36:06 +00:00
|
|
|
bool "Align linker sections up to SECTION_SIZE"
|
|
|
|
help
|
|
|
|
If this option is enabled, sections that may potentially be marked as
|
|
|
|
read only or non-executable will be aligned up to the section size of
|
|
|
|
the kernel. This prevents sections from being split into pages and
|
|
|
|
avoids a potential TLB penalty. The downside is an increase in
|
|
|
|
alignment and potentially wasted space. Turn on this option if
|
|
|
|
performance is more important than memory pressure.
|
|
|
|
|
arm64: enable CONFIG_SET_MODULE_RONX by default
The SET_MODULE_RONX protections are effectively the same as the
DEBUG_RODATA protections we enabled by default back in commit
57efac2f7108e325 ("arm64: enable CONFIG_DEBUG_RODATA by default"). It
seems unusual to have one but not the other.
As evidenced by the help text, the rationale appears to be that
SET_MODULE_RONX interacts poorly with tracing and patching, but both of
these make use of the insn framework, which takes SET_MODULE_RONX into
account. Any remaining issues are bugs which should be fixed regardless
of the default state of the option.
This patch enables DEBUG_SET_MODULE_RONX by default, and replaces the
help text with a new wording derived from the DEBUG_RODATA help text,
which better describes the functionality. Previously, the DEBUG_RODATA
entry was inconsistently indented with spaces, which are replaced with
tabs as with the other Kconfig entries.
Additionally, the wording of recommended defaults is made consistent for
all options. These are placed in a new paragraph, unquoted, as a full
sentence (with a period/full stop) as this appears to be the most common
form per $(git grep 'in doubt').
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Laura Abbott <labbott@fedoraproject.org>
Acked-by: Kees Cook <keescook@chromium.org>
Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2016-05-13 11:20:36 +00:00
|
|
|
If in doubt, say N.
|
2015-01-22 01:36:06 +00:00
|
|
|
|
2017-02-02 17:33:19 +00:00
|
|
|
config DEBUG_EFI
|
|
|
|
depends on EFI && DEBUG_INFO
|
|
|
|
bool "UEFI debugging"
|
|
|
|
help
|
|
|
|
Enable this option to include EFI specific debugging features into
|
|
|
|
the kernel that are only useful when using a debug build of the
|
|
|
|
UEFI firmware
|
|
|
|
|
2017-03-31 07:55:33 +00:00
|
|
|
config ARM64_RELOC_TEST
|
|
|
|
depends on m
|
|
|
|
tristate "Relocation testing module"
|
|
|
|
|
2015-03-30 20:13:41 +00:00
|
|
|
source "drivers/hwtracing/coresight/Kconfig"
|
2015-03-30 20:13:36 +00:00
|
|
|
|
2012-04-20 13:45:54 +00:00
|
|
|
endmenu
|