From 02f480cc262112128c6c8e279fd3048a94f2eb4a Mon Sep 17 00:00:00 2001 From: Andrey Konovalov Date: Wed, 21 Jun 2017 12:06:27 +0200 Subject: Update linux_kernel_reporting_bugs.md --- docs/linux_kernel_reporting_bugs.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (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 2d70ac2fb..b0316518f 100644 --- a/docs/linux_kernel_reporting_bugs.md +++ b/docs/linux_kernel_reporting_bugs.md @@ -6,9 +6,11 @@ Please report found bugs to the Linux kernel maintainers. To find out the list of maintainers responsible for a particular kernel subsystem, use the [get_maintainer.pl](https://github.com/torvalds/linux/blob/master/scripts/get_maintainer.pl) script: `./scripts/get_maintainer.pl -f guilty_file.c`. 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. +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 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. +Check that the reproducer works if you run it manually. + Make sure to also mention the exact kernel branch and revision. Many kernel mailing lists reject HTML formatted messages, so use the plain text mode when sending the report. -- cgit mrf-deployment