From 71f516782bb401fd3968fdfdb2d211f496cf73c1 Mon Sep 17 00:00:00 2001 From: Andrey Konovalov Date: Wed, 14 Jun 2017 17:03:53 +0200 Subject: docs: various improvements --- docs/linux_kernel_reporting_bugs.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/linux_kernel_reporting_bugs.md') diff --git a/docs/linux_kernel_reporting_bugs.md b/docs/linux_kernel_reporting_bugs.md index fde46057a..2d70ac2fb 100644 --- a/docs/linux_kernel_reporting_bugs.md +++ b/docs/linux_kernel_reporting_bugs.md @@ -1,4 +1,4 @@ -## Reporting Linux kernel bugs +# Reporting Linux kernel bugs Before reporting a bug make sure nobody else already reported it. The easiest way to do this is to search through the [syzkaller mailing list](https://groups.google.com/forum/#!forum/syzkaller) for key frames present in the kernel stack traces. @@ -7,6 +7,7 @@ To find out the list of maintainers responsible for a particular kernel subsyste Please also add `syzkaller@googlegroups.com` to the CC list. If the bug is reproducible, include the reproducer (C source if possible, otherwise a syzkaller program) and `.config` you used for your kernel. +If the reprocucer is available only in the form of a syzkaller program, please link [the instructions on how to execute them](executing_syzkaller_programs.md) in your report. Bugs without reproducers are way less likely to be triaged and fixed. Make sure to also mention the exact kernel branch and revision. -- cgit mrf-deployment