From 8f3b15c4213fbdd6918d7ddd9ffa9fd4a623dc49 Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Thu, 28 Nov 2024 11:02:58 +0100 Subject: docs: update reproduction instructions 1. Get rid of executing_syzkaller_programs.md as it now mostly overlaps with reproducing_crashes.md. 2. Update the instructions on building the kernel with syzbot compilers. 3. Update the links throughout the documentation. --- docs/internals.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/internals.md') diff --git a/docs/internals.md b/docs/internals.md index b4d893791..56802da34 100644 --- a/docs/internals.md +++ b/docs/internals.md @@ -63,7 +63,7 @@ This set may need to be extended if you are using a different kernel architectur `logN` files contain raw `syzkaller` logs and include kernel console output as well as programs executed before the crash. These logs can be fed to `syz-repro` tool for [crash location and minimization](reproducing_crashes.md), -or to `syz-execprog` tool for [manual localization](executing_syzkaller_programs.md). +or to `syz-execprog` tool for [manual localization](reproducing_crashes.md#from-execution-logs). `reportN` files contain post-processed and symbolized kernel crash reports (e.g. a KASAN report). Normally you need just 1 pair of these files (i.e. `log0` and `report0`), because they all presumably describe the same kernel bug. However, `syzkaller` saves up to 100 of them for the case when the crash is poorly reproducible, or if you just want to look at a set of crash reports to infer some similarities or differences. -- cgit mrf-deployment