diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2017-06-16 13:14:12 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-06-16 13:14:12 +0200 |
| commit | 0349e2fb7a33d76a6c1616011ad099a056d5d214 (patch) | |
| tree | a76589733f1f4159d794b5c35af6c5343337b4a2 /docs/linux_kernel_reporting_bugs.md | |
| parent | daf82c6d9e31b7e3d9329430288b8126c4e1f14a (diff) | |
| parent | 71f516782bb401fd3968fdfdb2d211f496cf73c1 (diff) | |
Merge pull request #233 from xairy/up-docs-improve-2
docs: various improvements
Diffstat (limited to 'docs/linux_kernel_reporting_bugs.md')
| -rw-r--r-- | docs/linux_kernel_reporting_bugs.md | 3 |
1 files changed, 2 insertions, 1 deletions
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. |