Patrick Georgi has submitted this change. ( https://review.coreboot.org/c/coreboot/+/55991 )
Change subject: Documentation: Remove KASAN from the project ideas list ......................................................................
Documentation: Remove KASAN from the project ideas list
This project is already implemented and therefore should not be mentioned anymore as a new project idea in the documentation.
Change-Id: I38c6e274e416b98485943d36536a57a14743945b Signed-off-by: Werner Zeh werner.zeh@siemens.com Reviewed-on: https://review.coreboot.org/c/coreboot/+/55991 Tested-by: build bot (Jenkins) no-reply@coreboot.org Reviewed-by: Paul Menzel paulepanter@mailbox.org Reviewed-by: Angel Pons th3fanbus@gmail.com --- M Documentation/contributing/project_ideas.md 1 file changed, 0 insertions(+), 19 deletions(-)
Approvals: build bot (Jenkins): Verified Paul Menzel: Looks good to me, but someone else must approve Angel Pons: Looks good to me, approved
diff --git a/Documentation/contributing/project_ideas.md b/Documentation/contributing/project_ideas.md index 141023f..2f6f738 100644 --- a/Documentation/contributing/project_ideas.md +++ b/Documentation/contributing/project_ideas.md @@ -66,25 +66,6 @@ ### Mentors * Timothy Pearson tpearson@raptorengineering.com
-## 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 werner.zeh@gmx.net - ## Port payloads to ARM, AArch64 or RISC-V While we have a rather big set of payloads for x86 based platforms, all other architectures are rather limited. Improve the situation by porting a payload