diff options
| author | Aleksandr Nogikh <nogikh@google.com> | 2024-11-28 11:02:58 +0100 |
|---|---|---|
| committer | Aleksandr Nogikh <nogikh@google.com> | 2024-11-29 14:35:53 +0000 |
| commit | 8f3b15c4213fbdd6918d7ddd9ffa9fd4a623dc49 (patch) | |
| tree | 5504bc5ee059ac50c9fc585efe196f59a26de424 /docs/internals.md | |
| parent | b5d2be89685d997057176b6647393ba33b431d78 (diff) | |
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.
Diffstat (limited to 'docs/internals.md')
| -rw-r--r-- | docs/internals.md | 2 |
1 files changed, 1 insertions, 1 deletions
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. |