From 50baa8818434f32b297972e75330bc71e12b64e7 Mon Sep 17 00:00:00 2001 From: Werner Zeh Date: Thu, 14 Feb 2019 13:15:38 +0100 Subject: [PATCH] Documentation: Add KASAN to the project ideas list Adding the Kernel Address Sanitizer feature to coreboot would help to find bugs. Change-Id: If00010e81147ec50e037678230df17c6888e40a2 Signed-off-by: Werner Zeh Reviewed-on: https://review.coreboot.org/c/31414 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel Reviewed-by: Patrick Georgi --- Documentation/contributing/project_ideas.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/Documentation/contributing/project_ideas.md b/Documentation/contributing/project_ideas.md index 0a39a88c64..1c23cc6bc7 100644 --- a/Documentation/contributing/project_ideas.md +++ b/Documentation/contributing/project_ideas.md @@ -72,3 +72,22 @@ code doesn't entirely break these architectures hardware is available. ### Mentors + +## Add Kernel Address Sanitizer functionality to coreboot +The Kernel Address Sanitizer (KASAN) is a runtime dynamic memory error detector. +The idea is to check every memory access (variables) for its validity +during runtime and find bugs like stack overflow or out-of-bounds accesses. +Implementing this stub into coreboot like "Undefined behavior sanitizer support" +would help to ensure code quality and make the runtime code more robust. + +### Requirements +* knowledge in the coreboot build system and the concept of stages +* the KASAN feature can be improved in a way so that the memory space needed + during runtime is not on a fixed address provided during compile time but + determined during runtime. For this to achieve a small patch to the GCC will + be helpful. Therefore minor GCC knowledge would be beneficial. +* Implementation can be initially done in QEMU and improved on different + mainboards and platforms + +### Mentors +* Werner Zeh