Home
last modified time | relevance | path

Searched refs:bug (Results 1 – 25 of 279) sorted by relevance

12345678910>>...12

/kernel/linux/linux-5.10/lib/
Dbug.c54 static inline unsigned long bug_addr(const struct bug_entry *bug) in bug_addr() argument
57 return bug->bug_addr; in bug_addr()
59 return (unsigned long)bug + bug->bug_addr_disp; in bug_addr()
70 struct bug_entry *bug = NULL; in module_find_bug() local
76 bug = mod->bug_table; in module_find_bug()
77 for (i = 0; i < mod->num_bugs; ++i, ++bug) in module_find_bug()
78 if (bugaddr == bug_addr(bug)) in module_find_bug()
81 bug = NULL; in module_find_bug()
85 return bug; in module_find_bug()
135 struct bug_entry *bug; in find_bug() local
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dreporting-bugs.rst17 If you've found a bug on a kernel version that isn't listed on kernel.org,
20 kernels, and see if you can reproduce the bug on that. It's preferable
21 to reproduce the bug on the latest -rc kernel.
32 increases your chances of getting your bug fixed. Simply posting to the
33 generic linux-kernel mailing list (LKML) may cause your bug report to be
46 bug report. Some maintainers prefer bugs to be reported via bugzilla
50 To find out where to send an emailed bug report, find your subsystem or
52 entries, and send your bug report to the person(s) listed in the "M:"
62 If it is a security bug, please copy the Security Contact listed in the
67 a bug in kernel.org bugzilla and send email to
[all …]
Dbug-bisect.rst1 Bisecting a bug
10 not confident in doing that please report the bug to your distribution vendor
17 Before you submit a bug report read
26 Finding patch that caused a bug
29 Using the provided tools with ``git`` makes finding bugs easy provided the bug
56 depending if the bug happened on the changeset you're testing
58 likely caused the bug.
Dsecurity-bugs.rst7 like to know when a security bug is found so that it can be fixed and
16 who will help verify the bug report and develop and release a fix.
22 As it is with any bug, the more information provided the easier it
49 if it is agreed that the criticality of the bug requires more time. The
57 reporter. This includes but is not limited to the original bug report
86 may delay the bug handling. If a reporter wishes to have a CVE identifier
Dsysfs-rules.rst33 system configuration bug you should not try to solve. For test cases,
60 is a bug in the application
82 bug in the application
89 like the "device"-link, is a bug in the application
129 ``/sys/block`` and ``/sys/class/block`` are not interchangeable is a bug in
137 a bug in the application.
147 a device in ``/sys/devices/`` is a bug in the application.
148 Accessing ``/sys/class/net/eth0/device`` is a bug in the application.
157 real child device directories in the ``/sys/devices`` tree is a bug in
170 access the chain of parents is a bug in the application.
/kernel/linux/linux-5.10/Documentation/translations/zh_CN/process/
Dcode-of-conduct-interpretation.rst69 使用 kernel.org bugzilla和其他子系统bugzilla 或bug跟踪工具的开发人员应该遵循
81 视为违反。然而，不适当的语言可以被视为一个bug；如果任何相关方提交补丁，
82 这样的bug将被更快地修复。当前属于用户/内核API的一部分的表达式，或者反映已
83 发布标准或规范中使用的术语的表达式，不被视为bug。
Dhowto.rst228 “没有人知道新内核何时会被发布，因为发布是根据已知bug的情况来决定
275 报告bug
279 户在这个工具中报告找到的所有bug。如何使用内核bugzilla的细节请访问：
284 文件里有一个很好的模板。它指导用户如何报告可能的内核bug以及需要提供哪些信息
288 利用bug报告
291 练习内核开发技能的最好办法就是修改其他人报告的bug。你不光可以帮助内核变
293 者感受到你的存在。修改bug是赢得其他开发者赞誉的最好办法，因为并不是很多
294 人都喜欢浪费时间去修改别人报告的bug。
296 要尝试修改已知的bug，请访问 http://bugzilla.kernel.org 网址。
D5.Posting.rst92 补丁，即使真正的bug在其他地方。只要有可能，添加新代码的补丁程序应该立即
126 bug搜寻人员想知道补丁是否负责他们正在追查的问题，想知道内核如何变化的用户。
131 一个bug，请引用引入该bug的commit（如果可能，请在引用commits时同时提供commit id
215 - 如果您正在修复一个bug，请考虑该修复是否应进入下一个稳定更新。如果是这样，
D6.Followthrough.rst115 在处理完任何回归之后，可能还有其他普通的bug需要处理。稳定期是修复这些错误并
120 别忘了，还有其他里程碑也可能会创建bug报告：下一个主线稳定版本，当著名的发行
Dsubmitting-patches.rst134 如果修补程序修复了一个记录的bug条目，请按编号和URL引用该bug条目。如果补丁来
139 bug的URL之外，还要总结需要提交补丁的相关讨论要点。
173 例如，如果你的改动里同时有bug修正和性能优化，那么把这些改动拆分到两个或
239 严重的bug，可以考虑短期暂停以允许分销商向用户发布补丁；在这种情况下，显然不应
466 我们。请注意，如果bug是以私有方式报告的，那么在使用Reported-by标记之前，请
599 将补丁与以前的相关讨论关联起来，例如，将bug修复程序链接到电子邮件和bug报告。
Dstable-api-nonsense.rst90 找到bug，或者找到更好的实现方式。一旦发现这些，他们就很快会去修改当前的
140 - 其他人会找到驱动中的bug并修复。
Dvolatile-considered-harmful.rst35 个bug。在正确设计的内核代码中，volatile能带来的仅仅是使事情变慢。
89 bug并且需要对这样的代码额外仔细检查。那些试图使用volatile的开发人员需要退一步想想
/kernel/linux/linux-5.10/arch/m68k/include/asm/
Dmmu_context.h126 goto bug; in load_ksp_mmu()
130 goto bug; in load_ksp_mmu()
134 goto bug; in load_ksp_mmu()
138 goto bug; in load_ksp_mmu()
142 goto bug; in load_ksp_mmu()
147 goto bug; in load_ksp_mmu()
165 bug: in load_ksp_mmu()
/kernel/linux/linux-5.10/Documentation/scsi/
DChangeLog.arcmsr9 ** 1.10.00.10 10/10/2004 Erich Chen bug fix for SMP & ioctl
10 ** 1.20.00.00 11/29/2004 Erich Chen bug fix with arcmsr_bus_reset when PHY error
11 ** 1.20.00.02 12/09/2004 Erich Chen bug fix with over 2T bytes RAID Volume
25 ** 1.20.00.07 3/23/2005 Erich Chen bug fix with arcmsr_scsi_host_template_init
29 ** bug fix enormous stack usage (Adrian Bunk's comment)
30 ** 1.20.00.08 6/23/2005 Erich Chen bug fix with abort command,
33 ** 1.20.00.09 9/12/2005 Erich Chen bug fix with abort command handling, firmware versi…
34 ** and firmware update notify for hardware bug fix
42 ** 1.20.00.12 9/30/2005 Erich Chen bug fix with 64bit platform's ccbs using if over 4G…
/kernel/linux/linux-5.10/arch/sh/kernel/
Dtraps.c92 const struct bug_entry *bug; in handle_BUG() local
99 bug = find_bug(bugaddr); in handle_BUG()
102 if (bug->flags & BUGFLAG_UNWINDER) in handle_BUG()
150 BUILD_TRAP_HANDLER(bug) in BUILD_TRAP_HANDLER() argument
/kernel/linux/linux-5.10/arch/mips/kernel/
Dr4k-bugs64.c121 int bug, fix, i; in check_mult_sh() local
143 bug = 0; in check_mult_sh()
146 bug = 1; in check_mult_sh()
148 if (bug == 0) { in check_mult_sh()
/kernel/linux/linux-5.10/arch/xtensa/mm/
Dtlb.c268 int bug = 0; in check_tlb_sanity() local
273 bug |= check_tlb_entry(w, e, true); in check_tlb_sanity()
276 bug |= check_tlb_entry(w, e, false); in check_tlb_sanity()
277 if (bug & TLB_INSANE) in check_tlb_sanity()
279 if (bug & TLB_SUSPICIOUS) in check_tlb_sanity()
/kernel/linux/linux-5.10/Documentation/translations/zh_CN/admin-guide/
Dindex.rst29 下面的一组文档，针对的是试图跟踪问题和bug的用户。
35 bug-hunting
36 bug-bisect
/kernel/linux/linux-5.10/Documentation/filesystems/
Dhpfs.rst195 unbalanced trees too :-) but both HPFS and HPFS386 contain bug that it rarely
215 marks them as short (and writes "minor fs error corrected"). This bug is not in
229 0.91 Fixed bug that caused shooting to memory when write_inode was called on
232 0.93 Fixed bug that locked up the machine when there were too many filenames
236 0.95 Fixed a bug that i_hpfs_parent_dir was not updated when moving files
238 1.91 Fixed a bug that chk_sectors failed when sectors were at the end of disk
240 Fixed a bug that could possibly happen (with very low probability) when
258 1.92 Corrected a bug when sync was called just before closing file
272 Fixed a bug that slowed down alloc and prevented allocating 100% space
273 (this bug was not destructive)
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/cifs/
Dauthors.rst39 - Vince Negri and Dave Stahl (for finding an important caching bug)
50 - Aurelien Aptel (for DFS SMB3 work and some key bug fixes)
51 - Ronnie Sahlberg (for SMB3 xattr work, bug fixes, and lots of great work on compounding)
53 - Sachin Prabhu (many bug fixes, including for reconnect, copy offload and security)
60 Thanks to those in the community who have submitted detailed bug reports
/kernel/linux/linux-5.10/include/linux/
Dbug.h34 static inline int is_warning_bug(const struct bug_entry *bug) in is_warning_bug() argument
36 return bug->flags & BUGFLAG_WARNING; in is_warning_bug()
/kernel/linux/linux-5.10/arch/ia64/
DKconfig.debug41 bool "Turn on compare-and-exchange bug checking (slow!)"
44 Selecting this option turns on bug checking for the IA-64
53 Selecting this option turns on bug checking for the IA-64 irq_save
/kernel/linux/linux-5.10/drivers/media/pci/saa7164/
Dsaa7164-bus.c73 int bug = 0; in saa7164_bus_verify() local
76 bug++; in saa7164_bus_verify()
79 bug++; in saa7164_bus_verify()
82 bug++; in saa7164_bus_verify()
85 bug++; in saa7164_bus_verify()
87 if (bug) { in saa7164_bus_verify()
/kernel/linux/linux-5.10/Documentation/translations/zh_CN/
Doops-tracing.txt1 Chinese translated version of Documentation/admin-guide/bug-hunting.rst
11 Documentation/admin-guide/bug-hunting.rst 的中文翻译
77 那是发现问题的简单办法，至少如果bug报告做的好的情况下（象这个一样-运行ksymoops
82 另一件要做的事是反汇编bug报告的“Code”部分：ksymoops也会用正确的工具来做这件事，
/kernel/linux/linux-5.10/tools/testing/ktest/
Dktest.pl1652 my $bug = 0;
1675 if (!$bug && !$skip_call_trace) {
1679 $bug = 1;
1689 $bug = 1;
1706 $bug = 1;
1708 return $bug;
2085 my $bug = 0;
2110 if ($bug && defined($stop_after_failure) &&
2160 if (!$bug && !$skip_call_trace) {
2164 $bug = 1;
[all …]

12345678910>>...12