docs: update reporting_kernel_bugs.md

Elaborate on report sanity.

1 files changed, 6 insertions, 1 deletions

diff --git a/docs/linux/reporting_kernel_bugs.md b/docs/linux/reporting_kernel_bugs.md
index f1989fe9f..689f7d67f 100644
--- a/docs/linux/reporting_kernel_bugs.md
+++ b/docs/linux/reporting_kernel_bugs.md
@@ -7,7 +7,12 @@ To find out the list of maintainers responsible for a particular kernel subsyste
 Make sure to mention the exact kernel branch and revision where the bug occurred.
 Many kernel mailing lists reject HTML formatted messages, so use the plain text mode when sending the report.
 
-Bugs without reproducers are way less likely to be triaged and fixed.
+Think of what you report. Today, Linux maintainers are overwhelmed with bug reports, so increasing the incoming flow won't help to fix all the bugs.
+The more actionable your report is, the higher the chance that it will be addressed.
+Note that people are more likely to care about kernel crashes (e.g. use-after-frees or panics) than of INFO: messages and such, unless it is clearly visible from the report what exactly is wrong.
+If there are stalls or hangs, only report them if they are frequent enough or have a reliable reproducer.
+
+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 reprocucer 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.
 Check that the reproducer works if you run it manually.