Documentation/admin-guide/reporting-bugs.rst

9 The upstream Linux kernel maintainers only fix bugs for specific kernel
10 versions.  Those versions include the current "release candidate" (or -rc)
11 kernel, any "stable" kernel versions, and any "long term" kernels.
13 Please see https://www.kernel.org/ for a list of supported kernels.  Any
14 kernel marked with [EOL] is "end of life" and will not have any fixes
17 If you've found a bug on a kernel version that isn't listed on kernel.org,
19 Alternatively, you can attempt to run one of the supported stable or -rc
21 to reproduce the bug on the latest -rc kernel.
24 How to report Linux kernel bugs
29 ----------------------------------
31 Identifying which part of the Linux kernel might be causing your issue
33 generic linux-kernel mailing list (LKML) may cause your bug report to be
34 lost in the noise of a mailing list that gets 1000+ emails a day.
36 Instead, try to figure out which kernel subsystem is causing the issue,
43 ----------------------
47 (https://bugzilla.kernel.org), while others prefer that bugs be reported
51 device driver in the MAINTAINERS file.  Search in the file for relevant
52 entries, and send your bug report to the person(s) listed in the "M:"
53 lines, making sure to Cc the mailing list(s) in the "L:" lines.  When the
54 maintainer replies to you, make sure to 'Reply-all' in order to keep the
55 public mailing list(s) in the email thread.
60      perl scripts/get_maintainer.pl -f <filename>
62 If it is a security bug, please copy the Security Contact listed in the
64 :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` for more information.
67 a bug in kernel.org bugzilla and send email to
68 linux-kernel@vger.kernel.org, referencing the bugzilla URL.  (For more
69 information on the linux-kernel mailing list see
70 http://vger.kernel.org/lkml/).
74 -----------------------
80 	http://www.catb.org/esr/faqs/smart-questions.html
89 ------------------
91 The most important information in a bug report is how to reproduce the
93 step-by-step instructions for how a user can trigger the bug.
97 report.  Please read "Documentation/admin-guide/bug-hunting.rst" before posting your
104 information they're really interested in.  If some information is not
109 the command ``awk -f scripts/ver_linux``.
111 Use that information to fill in all fields of the bug report form, and
117   [3.] Keywords (i.e., modules, networking, kernel):
118   [4.] Kernel information
119   [4.1.] Kernel version (from /proc/version):
120   [4.2.] Kernel .config file:
121   [5.] Most recent kernel version which did not have the bug:
123        resolved (see Documentation/admin-guide/bug-hunting.rst)
131   [8.5.] PCI information ('lspci -vvv' as root)
134          (please look in /proc and include all information that you
143 ------------------------------
145 Linux kernel maintainers expect bug reporters to be able to follow up on
147 recompiling your kernel, and/or re-triggering your bug.  The most
151 That said, it's still useful for a kernel maintainer to know a bug exists
152 on a supported kernel, even if you can't follow up with retests.  Follow
154 kernel and I can't reproduce my bug anymore" are also helpful, because
157 Expectations for kernel maintainers
158 -----------------------------------
160 Linux kernel maintainers are busy, overworked human beings.  Some times
161 they may not be able to address your bug in a day, a week, or two weeks.
167 In general, kernel maintainers take 1 to 5 business days to respond to
168 bugs.  The majority of kernel maintainers are employed to work on the
169 kernel, and they may not work on the weekends.  Maintainers are scattered
170 around the world, and they may not work in your time zone.  Unless you
174 The exceptions to this rule are regressions, kernel crashes, security holes,
175 or userspace breakage caused by new kernel behavior.  Those bugs should be
177 responding to these types of bugs in a timely manner (especially during a
182 [Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]