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/linux/reporting_kernel_bugs.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/linux/reporting_kernel_bugs.md')
| -rw-r--r-- | docs/linux/reporting_kernel_bugs.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/linux/reporting_kernel_bugs.md b/docs/linux/reporting_kernel_bugs.md index 78d182b05..f5859cf9d 100644 --- a/docs/linux/reporting_kernel_bugs.md +++ b/docs/linux/reporting_kernel_bugs.md @@ -42,7 +42,7 @@ If there are stalls or hangs, only report them if they are frequent enough or ha Overall, bugs without reproducers are way less likely to be triaged and fixed. If the bug is reproducible, include the reproducer (C source if possible, otherwise a syzkaller program) and the `.config` you used for your kernel. -If the reproducer is available only in the form of a syzkaller program, please link [the instructions on how to execute them](/docs/executing_syzkaller_programs.md) in your report. +If the reproducer is available only in the form of a syzkaller program, please link [the instructions on how to execute them](/docs/reproducing_crashes.md#using-a-c-reproducer) in your report. Check that the reproducer works if you run it manually. Syzkaller tries to simplify the reproducer, but the result might not be ideal. You can try to simplify or annotate the reproducer manually, that greatly helps kernel developers to figure out why the bug occurs. |