2012-04-20 20:45:54 +07:00
|
|
|
menu "Kernel hacking"
|
|
|
|
|
|
|
|
|
|
source "lib/Kconfig.debug"
|
|
|
|
|
|
2014-11-26 07:28:39 +07:00
|
|
|
config ARM64_PTDUMP
|
|
|
|
|
bool "Export kernel pagetable layout to userspace via debugfs"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
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 18:20:36 +07:00
|
|
|
|
|
|
|
|
If in doubt, say N.
|
2014-11-26 07:28:39 +07:00
|
|
|
|
2013-01-17 19:31:45 +07: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 22:51:37 +07: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.
|
|
|
|
|
|
2014-08-20 02:41:43 +07:00
|
|
|
config DEBUG_SET_MODULE_RONX
|
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 18:20:36 +07:00
|
|
|
bool "Set loadable kernel module data as NX and text as RO"
|
|
|
|
|
depends on MODULES
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Is this is set, kernel module text and rodata will be made read-only.
|
|
|
|
|
This is to help catch accidental or malicious attempts to change the
|
|
|
|
|
kernel's executable code.
|
|
|
|
|
|
|
|
|
|
If in doubt, say Y.
|
2014-08-20 02:41:43 +07:00
|
|
|
|
2015-01-22 08:36:06 +07:00
|
|
|
config DEBUG_RODATA
|
|
|
|
|
bool "Make kernel text and rodata read-only"
|
arm64: enable CONFIG_DEBUG_RODATA by default
In spite of its name, CONFIG_DEBUG_RODATA is an important hardening feature
for production kernels, and distros all enable it by default in their
kernel configs. However, since enabling it used to result in more granular,
and thus less efficient kernel mappings, it is not enabled by default for
performance reasons.
However, since commit 2f39b5f91eb4 ("arm64: mm: Mark .rodata as RO"), the
various kernel segments (.text, .rodata, .init and .data) are already
mapped individually, and the only effect of setting CONFIG_DEBUG_RODATA is
that the existing .text and .rodata mappings are updated late in the boot
sequence to have their read-only attributes set, which means that any
performance concerns related to enabling CONFIG_DEBUG_RODATA are no longer
valid.
So from now on, make CONFIG_DEBUG_RODATA default to 'y'
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-03-03 21:10:59 +07:00
|
|
|
default y
|
2015-01-22 08:36:06 +07:00
|
|
|
help
|
|
|
|
|
If this is set, kernel text and rodata will be made read-only. This
|
|
|
|
|
is to help catch accidental or malicious attempts to change the
|
arm64: enable CONFIG_DEBUG_RODATA by default
In spite of its name, CONFIG_DEBUG_RODATA is an important hardening feature
for production kernels, and distros all enable it by default in their
kernel configs. However, since enabling it used to result in more granular,
and thus less efficient kernel mappings, it is not enabled by default for
performance reasons.
However, since commit 2f39b5f91eb4 ("arm64: mm: Mark .rodata as RO"), the
various kernel segments (.text, .rodata, .init and .data) are already
mapped individually, and the only effect of setting CONFIG_DEBUG_RODATA is
that the existing .text and .rodata mappings are updated late in the boot
sequence to have their read-only attributes set, which means that any
performance concerns related to enabling CONFIG_DEBUG_RODATA are no longer
valid.
So from now on, make CONFIG_DEBUG_RODATA default to 'y'
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2016-03-03 21:10:59 +07:00
|
|
|
kernel's executable code.
|
2015-01-22 08:36:06 +07:00
|
|
|
|
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 18:20:36 +07:00
|
|
|
If in doubt, say Y.
|
2015-01-22 08:36:06 +07:00
|
|
|
|
|
|
|
|
config DEBUG_ALIGN_RODATA
|
arm64: simplify kernel segment mapping granularity
The mapping of the kernel consist of four segments, each of which is mapped
with different permission attributes and/or lifetimes. To optimize the TLB
and translation table footprint, we define various opaque constants in the
linker script that resolve to different aligment values depending on the
page size and whether CONFIG_DEBUG_ALIGN_RODATA is set.
Considering that
- a 4 KB granule kernel benefits from a 64 KB segment alignment (due to
the fact that it allows the use of the contiguous bit),
- the minimum alignment of the .data segment is THREAD_SIZE already, not
PAGE_SIZE (i.e., we already have padding between _data and the start of
the .data payload in many cases),
- 2 MB is a suitable alignment value on all granule sizes, either for
mapping directly (level 2 on 4 KB), or via the contiguous bit (level 3 on
16 KB and 64 KB),
- anything beyond 2 MB exceeds the minimum alignment mandated by the boot
protocol, and can only be mapped efficiently if the physical alignment
happens to be the same,
we can simplify this by standardizing on 64 KB (or 2 MB) explicitly, i.e.,
regardless of granule size, all segments are aligned either to 64 KB, or to
2 MB if CONFIG_DEBUG_ALIGN_RODATA=y. This also means we can drop the Kconfig
dependency of CONFIG_DEBUG_ALIGN_RODATA on CONFIG_ARM64_4K_PAGES.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2016-03-30 22:43:09 +07:00
|
|
|
depends on DEBUG_RODATA
|
2015-01-22 08:36:06 +07: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 18:20:36 +07:00
|
|
|
If in doubt, say N.
|
2015-01-22 08:36:06 +07:00
|
|
|
|
2015-03-31 03:13:41 +07:00
|
|
|
source "drivers/hwtracing/coresight/Kconfig"
|
2015-03-31 03:13:36 +07:00
|
|
|
|
2012-04-20 20:45:54 +07:00
|
|
|
endmenu
|