diff options
Diffstat (limited to 'REPORTING-BUGS')
-rw-r--r-- | REPORTING-BUGS | 42 |
1 files changed, 41 insertions, 1 deletions
diff --git a/REPORTING-BUGS b/REPORTING-BUGS index c1f6e43f06f3..327b33b43d63 100644 --- a/REPORTING-BUGS +++ b/REPORTING-BUGS | |||
@@ -117,4 +117,44 @@ summary from [1.]>" for easy identification by the developers. | |||
117 | [X.] Other notes, patches, fixes, workarounds: | 117 | [X.] Other notes, patches, fixes, workarounds: |
118 | 118 | ||
119 | 119 | ||
120 | Thank you | 120 | Follow up |
121 | ========= | ||
122 | |||
123 | Expectations for bug reporters | ||
124 | ------------------------------ | ||
125 | |||
126 | Linux kernel maintainers expect bug reporters to be able to follow up on | ||
127 | bug reports. That may include running new tests, applying patches, | ||
128 | recompiling your kernel, and/or re-triggering your bug. The most | ||
129 | frustrating thing for maintainers is for someone to report a bug, and then | ||
130 | never follow up on a request to try out a fix. | ||
131 | |||
132 | That said, it's still useful for a kernel maintainer to know a bug exists | ||
133 | on a supported kernel, even if you can't follow up with retests. Follow | ||
134 | up reports, such as replying to the email thread with "I tried the latest | ||
135 | kernel and I can't reproduce my bug anymore" are also helpful, because | ||
136 | maintainers have to assume silence means things are still broken. | ||
137 | |||
138 | Expectations for kernel maintainers | ||
139 | ----------------------------------- | ||
140 | |||
141 | Linux kernel maintainers are busy, overworked human beings. Some times | ||
142 | they may not be able to address your bug in a day, a week, or two weeks. | ||
143 | If they don't answer your email, they may be on vacation, or at a Linux | ||
144 | conference. Check the conference schedule at LWN.net for more info: | ||
145 | https://lwn.net/Calendar/ | ||
146 | |||
147 | In general, kernel maintainers take 1 to 5 business days to respond to | ||
148 | bugs. The majority of kernel maintainers are employed to work on the | ||
149 | kernel, and they may not work on the weekends. Maintainers are scattered | ||
150 | around the world, and they may not work in your time zone. Unless you | ||
151 | have a high priority bug, please wait at least a week after the first bug | ||
152 | report before sending the maintainer a reminder email. | ||
153 | |||
154 | The exceptions to this rule are regressions, kernel crashes, security holes, | ||
155 | or userspace breakage caused by new kernel behavior. Those bugs should be | ||
156 | addressed by the maintainers ASAP. If you suspect a maintainer is not | ||
157 | responding to these types of bugs in a timely manner (especially during a | ||
158 | merge window), escalate the bug to LKML and Linus Torvalds. | ||
159 | |||
160 | Thank you! | ||