aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/stackleak.c
diff options
context:
space:
mode:
authorAlexander Popov <alex.popov@linux.com>2020-06-24 15:33:27 +0300
committerKees Cook <keescook@chromium.org>2020-06-24 07:48:27 -0700
commitddfaf0e43e9bd4341dc2c24d48ac218f2fb1530a (patch)
tree852de6402040c64b01d3c83bb1f0159119c9802a /kernel/stackleak.c
parentgcc-plugins/stackleak: Don't instrument itself (diff)
downloadlinux-dev-ddfaf0e43e9bd4341dc2c24d48ac218f2fb1530a.tar.xz
linux-dev-ddfaf0e43e9bd4341dc2c24d48ac218f2fb1530a.zip
ARM: vdso: Don't use gcc plugins for building vgettimeofday.c
Don't use gcc plugins for building arch/arm/vdso/vgettimeofday.c to avoid unneeded instrumentation. As previously discussed[1]: arm_ssp_per_task_plugin.c 32-bit ARM only (but likely needs disabling for 32-bit ARM vDSO?) cyc_complexity_plugin.c compile-time reporting only latent_entropy_plugin.c this shouldn't get triggered for the vDSO (no __latent_entropy nor __init attributes in vDSO), but perhaps explicitly disabling it would be a sensible thing to do, just for robustness? randomize_layout_plugin.c this shouldn't get triggered (again, lacking attributes), but should likely be disabled too. sancov_plugin.c This should be tracking the KCOV directly (see scripts/Makefile.kcov), which is already disabled here. structleak_plugin.c This should be fine in the vDSO, but there's no security boundary here, so it wouldn't be important to KEEP it enabled. [1] https://lore.kernel.org/lkml/20200610073046.GA15939@willie-the-truck/ Signed-off-by: Alexander Popov <alex.popov@linux.com> Link: https://lore.kernel.org/r/20200624123330.83226-3-alex.popov@linux.com Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'kernel/stackleak.c')
0 files changed, 0 insertions, 0 deletions