| /linux/Documentation/process/ |
| H A D | security-bugs.rst | 3 Security bugs
8 disclosed as quickly as possible. Please report security bugs to the
43 for publicly known bugs are released immediately.
45 Although our preference is to release fixes for publicly undisclosed bugs
61 In other words our only interest is in getting bugs fixed. All other
69 While the kernel security team solely focuses on getting bugs fixed,
|
| H A D | index.rst | 72 Dealing with bugs
75 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
|
| H A D | maintainer-kvm-x86.rst | 42 in-flight commits' SHA1 hashes, and having to reject a pull request due to bugs
90 rule, but typically only fixes for bugs that are urgent, critical, and/or were
218 the most simple bugs require multiple sentences or paragraphs to fully describe
296 Except for "obvious" found-by-inspection bugs, fixes must be accompanied by a
300 bugs that are found via non-public workloads/tests, but providing regression
301 tests for such bugs is strongly preferred.
308 Note, KVM bugs are rarely urgent *and* non-trivial to reproduce. Ask yourself
352 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
|
| H A D | cve.rst | 19 process<../process/security-bugs>`.
51 process<../process/security-bugs>`.
115 individual cherry-picked changes. Also note that for many bugs, the
|
| /linux/include/linux/ |
| H A D | serial_8250.h | 21 * @bugs: Port bugs
48 u16 bugs; /* port bugs */ member
129 u16 bugs; /* port bugs */ member
|
| /linux/drivers/net/ethernet/chelsio/ |
| H A D | Kconfig | 37 Please send feedback to <linux-bugs@chelsio.com>.
64 Please send feedback to <linux-bugs@chelsio.com>.
87 Please send feedback to <linux-bugs@chelsio.com>.
128 Please send feedback to <linux-bugs@chelsio.com>.
|
| /linux/Documentation/arch/x86/ |
| H A D | pti.rst | 147 is known to trigger bugs in code paths that did not expect to be
162 Bugs in PTI cause a few different signatures of crashes
167 * Crashes in early boot, especially around CPU bringup. Bugs
169 * Crashes at the first interrupt. Caused by bugs in entry_64.S,
173 interrupt handlers and can have bugs that do not affect
179 bugs, or failing to map some of the exit code.
|
| /linux/Documentation/fb/ |
| H A D | aty128fb.rst | 69 There are known and unknown bugs, features and misfeatures.
70 Currently there are following known bugs:
73 bugs/errata to list here.
|
| /linux/Documentation/tools/rtla/ |
| H A D | common_appendix.rst | 1 REPORTING BUGS
3 Report bugs to <linux-kernel@vger.kernel.org>
|
| /linux/Documentation/tools/rv/ |
| H A D | common_appendix.rst | 1 REPORTING BUGS
4 Report bugs to <linux-kernel@vger.kernel.org>
|
| /linux/drivers/scsi/aic7xxx/ |
| H A D | aic79xx.seq | 51 if ((ahd->bugs & AHD_INTCOLLISION_BUG) != 0) {
58 if ((ahd->bugs & AHD_INTCOLLISION_BUG) != 0) {
124 if ((ahd->bugs & AHD_FAINT_LED_BUG) != 0) {
298 if ((ahd->bugs & AHD_PKT_LUN_BUG) != 0) {
520 if ((ahd->bugs & AHD_SET_MODE_BUG) != 0) {
528 if ((ahd->bugs & AHD_INTCOLLISION_BUG) != 0) {
539 if ((ahd->bugs & AHD_SENT_SCB_UPDATE_BUG) != 0) {
594 if ((ahd->bugs & AHD_NONPACKFIFO_BUG) != 0) {
618 if ((ahd->bugs & AHD_FAINT_LED_BUG) != 0) {
633 if ((ahd->bugs & AHD_BUSFREEREV_BUG) != 0) {
[all …]
|
| /linux/drivers/parport/ |
| H A D | TODO-parport | 3 0. Fix the bugs (see BUGS-parport).
|
| /linux/lib/ |
| H A D | test_linear_ranges.c | 14 * to kill bugs get to decide how a company should implement testing strategy...
18 * bugs. This may lead to ideas about demands to get certain % of "test
28 * working, your test must not assume it is working. You won't catch any bugs
31 * does these tests - which are not finding any bugs now - do?
|
| /linux/Documentation/RCU/ |
| H A D | rcu_dereference.rst | 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 compiler
490 Unfortunately, these sorts of bugs can be extremely hard to spot during
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | cve.rst | 17 独立于 :doc:`安全漏洞报送流程</process/security-bugs>`。
40 </process/security-bugs>` 发送到Linux内核社区。
|
| /linux/kernel/rcu/ |
| H A D | Kconfig.debug | 118 printing the RCU CPU stall warning. As such, bugs in notifier
151 bugs in arch-specific NO_HZ code.
168 when looking for certain types of RCU usage bugs, for example,
|
| /linux/Documentation/dev-tools/ |
| H A D | testing-overview.rst | 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 tests
156 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.
|
| /linux/Documentation/filesystems/bcachefs/ |
| H A D | CodingStyle.rst | 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 bugs
108 better behaved; often one bug will uncover several other bugs through
|
| /linux/arch/x86/kernel/ |
| H A D | smp.c | 40 * Some notes on x86 processor bugs affecting SMP operation:
42 * Pentium, Pentium Pro, II, III (and all CPUs) have bugs.
113 * If this sounds worrying believe me these bugs are either ___RARE___,
114 * or are signal timing bugs worked around in hardware and there's
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | todo.rst | 87 s) Addressing bugs found by running a broader set of xfstests in standard
104 Known Bugs
131 6) Address various coverity warnings (most are not bugs per-se, but
|
| /linux/sound/soc/codecs/ |
| H A D | ad73311.h | 13 * Bugs: Enter bugs at http://blackfin.uclinux.org/
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 43 history; used improperly, it can obscure that history and introduce bugs.
74 increases the chances of running into surprising bugs. When a patch
150 branch. They will significantly increase your chances of encountering bugs
196 bringing in other bugs and should almost never be done. If that subsystem
|
| H A D | modifying-patches.rst | 12 one submitters code and make him endorse your bugs. To solve this problem, it
49 tracking your trees, and to people trying to troubleshoot bugs in your
|
| /linux/Documentation/usb/ |
| H A D | CREDITS | 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
|
| /linux/tools/testing/selftests/arm64/signal/ |
| H A D | README | 39 unrelated SEGV bugs in the testcases, it becomes extremely tricky to
41 to address and they are not instead falling apart due to unplanned bugs
|