aboutsummaryrefslogtreecommitdiffstats
path: root/docs/linux_kernel_reporting_bugs.md
diff options
context:
space:
mode:
authorAndrey Konovalov <andreyknvl@gmail.com>2017-06-14 14:13:36 +0200
committerGitHub <noreply@github.com>2017-06-14 14:13:36 +0200
commitfbec6b14d43b3885014393d928daa3ef2bbb1e8e (patch)
tree4ac9abbbd2216e56e8eb058ef26b2c146f595ac9 /docs/linux_kernel_reporting_bugs.md
parent7b96fa44e1a1b0c6c6369f899b378eee7583a419 (diff)
parent4731d5a4ac84accb8f4c3e224816d81055041e2b (diff)
Merge pull request #231 from xairy/up-docs
Move all documentation to docs/
Diffstat (limited to 'docs/linux_kernel_reporting_bugs.md')
-rw-r--r--docs/linux_kernel_reporting_bugs.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/linux_kernel_reporting_bugs.md b/docs/linux_kernel_reporting_bugs.md
new file mode 100644
index 000000000..fde46057a
--- /dev/null
+++ b/docs/linux_kernel_reporting_bugs.md
@@ -0,0 +1,15 @@
+## 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.
+
+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.
+Bugs without reproducers are way less likely to be triaged and fixed.
+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.
+
+If you believe that a found bug poses potential security threat, consider reporting it directly to `security@kernel.org`.