Lines Matching refs:bug

17 If you've found a bug on a kernel version that isn't listed on kernel.org,
20 kernels, and see if you can reproduce the bug on that.  It's preferable
21 to reproduce the bug on the latest -rc kernel.
32 increases your chances of getting your bug fixed. Simply posting to the
33 generic linux-kernel mailing list (LKML) may cause your bug report to be
46 bug report.  Some maintainers prefer bugs to be reported via bugzilla
50 To find out where to send an emailed bug report, find your subsystem or
52 entries, and send your bug report to the person(s) listed in the "M:"
62 If it is a security bug, please copy the Security Contact listed in the
67 a bug in kernel.org bugzilla and send email to
76 If you haven't reported a bug before, please read:
91 The most important information in a bug report is how to reproduce the
92 bug.  This includes system information, and (most importantly)
93 step-by-step instructions for how a user can trigger the bug.
96 a netconsole trace, or type the message from your screen into the bug
97 report.  Please read "Documentation/admin-guide/bug-hunting.rst" before posting your
98 bug report. This explains what you should do with the "Oops" information
101 This is a suggested format for a bug report sent via email or bugzilla.
102 Having a standardized bug report form makes it easier for you not to
105 relevant to your bug, feel free to exclude it.
111 Use that information to fill in all fields of the bug report form, and
121   [5.] Most recent kernel version which did not have the bug:
123        resolved (see Documentation/admin-guide/bug-hunting.rst)
142 Expectations for bug reporters
145 Linux kernel maintainers expect bug reporters to be able to follow up on
146 bug reports.  That may include running new tests, applying patches,
147 recompiling your kernel, and/or re-triggering your bug.  The most
148 frustrating thing for maintainers is for someone to report a bug, and then
151 That said, it's still useful for a kernel maintainer to know a bug exists
154 kernel and I can't reproduce my bug anymore" are also helpful, because
161 they may not be able to address your bug in a day, a week, or two weeks.
171 have a high priority bug, please wait at least a week after the first bug
178 merge window), escalate the bug to LKML and Linus Torvalds.