| /linux/tools/testing/selftests/x86/bugs/ |
| H A D | common.py | 7 # mitigation for x86 bugs.
58 def sysfs_has_either(bugs, mitigations): argument
59 for bug in bugs:
65 def sysfs_has_none(bugs, mitigations): argument
66 return not sysfs_has_either(bugs, mitigations)
68 def sysfs_has_all(bugs, mitigations): argument
69 for bug in bugs:
|
| /linux/Documentation/process/ |
| H A D | security-bugs.rst | 3 Security bugs
21 will not be processed. A significant part of reports are for bugs that
72 It is important that most bugs are handled publicly so as to involve the widest
73 possible audience and find the best solution. By nature, bugs that are handled
78 It turns out that the majority of the bugs reported via the security team are
79 just regular bugs that have been improperly qualified as security bugs due to
85 The security list exists for urgent bugs that grant an attacker a capability
93 team's experience shows that bugs discovered this way systematically surface
101 a real vulnerability. Reporting ordinary bugs to the security list, however,
170 Responsible use of AI to find bugs
[all …]
|
| H A D | threat-model.rst | 6 (:doc:`security-related ones <security-bugs>` vs :doc:`non-security ones
30 When hardware fails to maintain its specified isolation (e.g., CPU bugs,
94 Bugs that permit to violate the principles above constitute security breaches.
95 However, bugs that permit one violation only once another one was already
98 classes of bugs are found, but a failure of these extra protections do not
105 **NOT** considered as Linux Kernel security bugs. However, when it is believed
211 exploitable vector and are not security bugs, though they must be reported
216 * bugs triggered by mounting a corrupted or maliciously crafted file system
217 image are generally not security bugs, as the kernel assumes the underlying
|
| H A D | index.rst | 75 Dealing with bugs
78 Bugs are a fact of life; it is important that we handle them properly. The
80 policies around the handling of a couple of special classes of bugs:
88 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/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 | 67 There are known and unknown bugs, features and misfeatures.
68 Currently there are following known bugs:
71 bugs/errata to list here.
|
| /linux/Documentation/tools/rv/ |
| H A D | common_appendix.rst | 1 REPORTING BUGS
4 Report bugs to <linux-kernel@vger.kernel.org>
|
| /linux/drivers/parport/ |
| H A D | TODO-parport | 3 0. Fix the bugs (see BUGS-parport).
|
| /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/Documentation/translations/zh_CN/process/ |
| H A D | cve.rst | 17 独立于 :doc:`安全漏洞报送流程</process/security-bugs>`。
40 </process/security-bugs>` 发送到Linux内核社区。
|
| /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/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/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/lib/crypto/tests/ |
| H A D | poly1305_kunit.c | 65 * detecting bugs that occur only in rare cases where the accumulator values
69 * Accumulator overflow bugs may be specific to particular update lengths (in
113 * edge case bugs in the modular reduction logic.
|
| /linux/tools/testing/selftests/mm/ |
| H A D | vm_util.h | 68 * Plan 9 FS has bugs (at least on QEMU) where certain operations fail with
71 * bugs. There are rumours of NFS implementations with similar bugs.
|
| /linux/sound/soc/codecs/ |
| H A D | ad73311.h | 13 * Bugs: Enter bugs at http://blackfin.uclinux.org/
|
| /linux/Documentation/maintainer/ |
| 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
|
| 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
|
| /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
|
| /linux/drivers/acpi/ |
| H A D | video_detect.c | 184 /* https://bugs.launchpad.net/bugs/1000146 */
209 /* https://bugs.launchpad.net/bugs/1000146 */
366 /* https://bugs.freedesktop.org/show_bug.cgi?id=81515 */
420 /* https://bugs.freedesktop.org/show_bug.cgi?id=87286 */
457 /* https://bugs.launchpad.net/bugs/1894667 */
840 /* Portégé: https://bugs.freedesktop.org/show_bug.cgi?id=82634 */
|
| /linux/Documentation/admin-guide/ |
| H A D | rapidio.rst | 20 Known Bugs and Limitations
23 Bugs section in Known Bugs and Limitations
|
| /linux/Documentation/nvme/ |
| H A D | feature-and-quirk-policy.rst | 35 bugs. Hence there is an inherent tradeoff between functionality and
64 implementation bugs. The intent of quirks is to deal with widely available
|