Searched full:bugs (Results 1 – 25 of 1555) sorted by relevance
12345678910>>...63
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 3 Reporting bugs
9 The upstream Linux kernel maintainers only fix bugs for specific kernel
24 How to report Linux kernel bugs
46 bug report. Some maintainers prefer bugs to be reported via bugzilla
47 (https://bugzilla.kernel.org), while others prefer that bugs be reported
64 :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` for more information.
73 Tips for reporting bugs
78 https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
82 It's REALLY important to report bugs that seem unrelated as separate email
84 bugs at once, it's difficult for maintainers to tease apart the relevant
[all …]
|
| D | security-bugs.rst | 3 Security bugs
8 disclosed as quickly as possible. Please report security bugs to the
24 :doc:`reporting-bugs` if you are unclear about what
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
|
| D | index.rst | 31 problems and bugs in particular.
36 reporting-bugs
37 security-bugs
|
| D | bug-bisect.rst | 13 Finding bugs is not always easy. Have a go though. If you can't find it don't
18 :ref:`Documentation/admin-guide/reporting-bugs.rst <reportingbugs>`.
29 Using the provided tools with ``git`` makes finding bugs easy provided the bug
|
| /kernel/linux/linux-5.10/arch/s390/include/asm/ |
| D | bugs.h | 7 * Derived from "include/asm-i386/bugs.h"
12 * This is included by init/main.c to check for architecture-dependent bugs.
20 /* s390 has no bugs ... */ in check_bugs()
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| 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
|
| 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
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | serial_8250.h | 21 * @bugs: Port bugs
48 u16 bugs; /* port bugs */ member
129 u16 bugs; /* port bugs */ member
|
| /kernel/linux/linux-5.10/Documentation/translations/zh_CN/ |
| D | SecurityBugs | 1 Chinese translated version of Documentation/admin-guide/security-bugs.rst
11 Documentation/admin-guide/security-bugs.rst 的中文翻译
34 是有帮助的信息，那就请重温一下admin-guide/reporting-bugs.rst文件中的概述过程。任
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/chelsio/ |
| 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>.
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/chelsio/ |
| D | Kconfig | 37 Please send feedback to <linux-bugs@chelsio.com>.
64 Please send feedback to <linux-bugs@chelsio.com>.
86 Please send feedback to <linux-bugs@chelsio.com>.
127 Please send feedback to <linux-bugs@chelsio.com>.
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | pti.rst | 149 is known to trigger bugs in code paths that did not expect to be
164 Bugs in PTI cause a few different signatures of crashes
169 * Crashes in early boot, especially around CPU bringup. Bugs
171 * Crashes at the first interrupt. Caused by bugs in entry_64.S,
175 interrupt handlers and can have bugs that do not affect
181 bugs, or failing to map some of the exit code.
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | pti.rst | 149 is known to trigger bugs in code paths that did not expect to be
164 Bugs in PTI cause a few different signatures of crashes
169 * Crashes in early boot, especially around CPU bringup. Bugs
171 * Crashes at the first interrupt. Caused by bugs in entry_64.S,
175 interrupt handlers and can have bugs that do not affect
181 bugs, or failing to map some of the exit code.
|
| /kernel/linux/linux-6.6/Documentation/tools/rv/ |
| D | common_appendix.rst | 1 REPORTING BUGS
4 Report bugs to <linux-kernel@vger.kernel.org>
|
| /kernel/linux/linux-6.6/Documentation/tools/rtla/ |
| D | common_appendix.rst | 1 REPORTING BUGS
3 Report bugs to <linux-kernel@vger.kernel.org>
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/fb/ |
| 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.
|
| /kernel/linux/linux-5.10/drivers/parport/ |
| D | TODO-parport | 3 0. Fix the bugs (see BUGS-parport).
|
| /kernel/linux/linux-6.6/drivers/parport/ |
| D | TODO-parport | 3 0. Fix the bugs (see BUGS-parport).
|
| /kernel/linux/linux-5.10/Documentation/translations/zh_CN/admin-guide/ |
| D | index.rst | 33 reporting-bugs
34 security-bugs
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_TW/admin-guide/ |
| D | index.rst | 40 security-bugs
48 reporting-bugs
|
| /kernel/linux/linux-5.10/drivers/scsi/aic7xxx/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/scsi/aic7xxx/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | rcu_dereference.rst | 17 bugs due to games that compilers and DEC Alpha can play.
53 again possibly resulting in bugs due to misordering.
85 result in misordering bugs.
107 rcu_dereference(). This could result in bugs due to misordering.
160 bugs more likely to happen. Which can be a good thing,
422 pointers, which can result in "interesting" bugs due to compiler
451 Unfortunately, these sorts of bugs can be extremely hard to spot during
|
| /kernel/linux/linux-5.10/lib/ |
| 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?
|
12345678910>>...63