Searched full:bugs (Results 1 – 25 of 207) sorted by relevance
123456789
1 REPORTING BUGS3 Report bugs to <linux-kernel@vger.kernel.org>
1 REPORTING BUGS4 Report bugs to <linux-kernel@vger.kernel.org>
3 Security bugs8 disclosed as quickly as possible. Please report security bugs to the43 for publicly known bugs are released immediately.45 Although our preference is to release fixes for publicly undisclosed bugs61 In other words our only interest is in getting bugs fixed. All other69 While the kernel security team solely focuses on getting bugs fixed,
72 Dealing with bugs75 Bugs are a fact of life; it is important that we handle them properly.77 of special classes of bugs: regressions and security problems.83 security-bugs
42 in-flight commits' SHA1 hashes, and having to reject a pull request due to bugs90 rule, but typically only fixes for bugs that are urgent, critical, and/or were218 the most simple bugs require multiple sentences or paragraphs to fully describe296 Except for "obvious" found-by-inspection bugs, fixes must be accompanied by a300 bugs that are found via non-public workloads/tests, but providing regression301 tests for such bugs is strongly preferred.308 Note, KVM bugs are rarely urgent *and* non-trivial to reproduce. Ask yourself352 tests that fail due to KVM bugs should be ordered after the KVM fixes.386 Bugs that can be exploited by the guest to attack the host (kernel or
19 process<../process/security-bugs>`.51 process<../process/security-bugs>`.115 individual cherry-picked changes. Also note that for many bugs, the
69 There are known and unknown bugs, features and misfeatures.70 Currently there are following known bugs:73 bugs/errata to list here.
17 独立于 :doc:`安全漏洞报送流程</process/security-bugs>`。40 </process/security-bugs>` 发送到Linux内核社区。
147 is known to trigger bugs in code paths that did not expect to be162 Bugs in PTI cause a few different signatures of crashes167 * Crashes in early boot, especially around CPU bringup. Bugs169 * Crashes at the first interrupt. Caused by bugs in entry_64.S,173 interrupt handlers and can have bugs that do not affect179 bugs, or failing to map some of the exit code.
12 one submitters code and make him endorse your bugs. To solve this problem, it49 tracking your trees, and to people trying to troubleshoot bugs in your
43 history; used improperly, it can obscure that history and introduce bugs.74 increases the chances of running into surprising bugs. When a patch150 branch. They will significantly increase your chances of encountering bugs196 bringing in other bugs and should almost never be done. If that subsystem
3 :Original: :ref:`Documentation/process/security-bugs.rst <securitybugs>`
33 problems and bugs in particular.41 verify-bugs-and-bisect-regressions
20 Known Bugs and Limitations23 Bugs section in Known Bugs and Limitations
25 security-bugs
35 bugs. Hence there is an inherent tradeoff between functionality and64 implementation bugs. The intent of quirks is to deal with widely available
66 bugs in error paths. Valuable suggestions also have come from Al Viro69 …er test teams and SuSE and Citrix and RedHat testers for finding multiple bugs during excellent st…
87 s) Addressing bugs found by running a broader set of xfstests in standard104 Known Bugs131 6) Address various coverity warnings (most are not bugs per-se, but
90 each look for a different class of bugs, such as invalid memory accesses,143 to avoid certain bugs that occur in common code patterns. The types of tests156 cause endianness bugs, detecting places that use ``__user`` pointers improperly,171 pre-processor so it's easier to check for bugs in macros using Coccinelle.
21 for bugs to hide.41 required to shake out bugs.105 rush to fix the initial issue. Look for things that will make related bugs108 better behaved; often one bug will uncover several other bugs through
127 pointing out mortal bugs and giving advice.150 pointed bugs, as well as started the uusbd-utils package.152 - Peter Dettori <dettori@ozy.dec.com> is uncovering bugs like
43 determining that bugs still exist; but are virtually useless when45 expect quick action. Bugs still exist. The problem remains in isolating
30 bugs due to games that compilers and DEC Alpha can play.73 again possibly resulting in bugs due to misordering.105 result in misordering bugs.127 rcu_dereference(). This could result in bugs due to misordering.186 bugs more likely to happen. Which can be a good thing,461 pointers, which can result in "interesting" bugs due to compiler490 Unfortunately, these sorts of bugs can be extremely hard to spot during
5 :Original: :doc:`../../../process/security-bugs`
34 Contact: Narendra K <Narendra.K@dell.com>, linux-bugs@dell.com