Home
last modified time | relevance | path

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

12345678910>>...12

/linux-6.1.9/lib/
Dbug.c53 static inline unsigned long bug_addr(const struct bug_entry *bug) in bug_addr() argument
56 return (unsigned long)&bug->bug_addr_disp + bug->bug_addr_disp; in bug_addr()
58 return bug->bug_addr; in bug_addr()
69 struct bug_entry *bug = NULL; in module_find_bug() local
75 bug = mod->bug_table; in module_find_bug()
76 for (i = 0; i < mod->num_bugs; ++i, ++bug) in module_find_bug()
77 if (bugaddr == bug_addr(bug)) in module_find_bug()
80 bug = NULL; in module_find_bug()
84 return bug; in module_find_bug()
129 void bug_get_file_line(struct bug_entry *bug, const char **file, in bug_get_file_line() argument
[all …]
/linux-6.1.9/Documentation/translations/zh_CN/process/
Dcode-of-conduct-interpretation.rst69 使用 kernel.org bugzilla和其他子系统bugzilla 或bug跟踪工具的开发人员应该遵循
81 视为违反。然而，不适当的语言可以被视为一个bug；如果任何相关方提交补丁，
82 这样的bug将被更快地修复。当前属于用户/内核API的一部分的表达式，或者反映已
83 发布标准或规范中使用的术语的表达式，不被视为bug。
Dhowto.rst227 “没有人知道新内核何时会被发布，因为发布是根据已知bug的情况来决定
274 报告bug
278 户在这个工具中报告找到的所有bug。如何使用内核bugzilla的细节请访问：
283 文件里有一个很好的模板。它指导用户如何报告可能的内核bug以及需要提供哪些信息
287 利用bug报告
290 练习内核开发技能的最好办法就是修改其他人报告的bug。你不光可以帮助内核变
292 者感受到你的存在。修改bug是赢得其他开发者赞誉的最好办法，因为并不是很多
293 人都喜欢浪费时间去修改别人报告的bug。
295 要尝试修改已知的bug，请访问 http://bugzilla.kernel.org 网址。
Dstable-api-nonsense.rst90 找到bug，或者找到更好的实现方式。一旦发现这些，他们就很快会去修改当前的
140 - 其他人会找到驱动中的bug并修复。
/linux-6.1.9/Documentation/translations/zh_TW/process/
Dcode-of-conduct-interpretation.rst72 使用 kernel.org bugzilla和其他子系統bugzilla 或bug跟蹤工具的開發人員應該遵循
84 視爲違反。然而，不適當的語言可以被視爲一個bug；如果任何相關方提交補丁，
85 這樣的bug將被更快地修復。當前屬於用戶/內核API的一部分的表達式，或者反映已
86 發布標準或規範中使用的術語的表達式，不被視爲bug。
Dhowto.rst230 「沒有人知道新內核何時會被發布，因爲發布是根據已知bug的情況來決定
277 報告bug
281 戶在這個工具中報告找到的所有bug。如何使用內核bugzilla的細節請訪問：
286 文件里有一個很好的模板。它指導用戶如何報告可能的內核bug以及需要提供哪些信息
290 利用bug報告
293 練習內核開發技能的最好辦法就是修改其他人報告的bug。你不光可以幫助內核變
295 者感受到你的存在。修改bug是贏得其他開發者讚譽的最好辦法，因爲並不是很多
296 人都喜歡浪費時間去修改別人報告的bug。
298 要嘗試修改已知的bug，請訪問 http://bugzilla.kernel.org 網址。
Dsubmitting-patches.rst135 如果修補程序修復了一個記錄的bug條目，請按編號和URL引用該bug條目。如果補丁來
140 bug的URL之外，還要總結需要提交補丁的相關討論要點。
174 例如，如果你的改動里同時有bug修正和性能優化，那麼把這些改動拆分到兩個或
240 嚴重的bug，可以考慮短期暫停以允許分銷商向用戶發布補丁；在這種情況下，顯然不應
443 我們。請注意，如果bug是以私有方式報告的，那麼在使用Reported-by標記之前，請
576 將補丁與以前的相關討論關聯起來，例如，將bug修復程序連結到電子郵件和bug報告。
Dstable-api-nonsense.rst93 找到bug，或者找到更好的實現方式。一旦發現這些，他們就很快會去修改當前的
143 - 其他人會找到驅動中的bug並修復。
/linux-6.1.9/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()
39 void bug_get_file_line(struct bug_entry *bug, const char **file,
65 static inline void bug_get_file_line(struct bug_entry *bug, const char **file, in bug_get_file_line() argument
/linux-6.1.9/Documentation/admin-guide/
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.
/linux-6.1.9/arch/m68k/include/asm/
Dmmu_context.h122 goto bug; in load_ksp_mmu()
126 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()
143 goto bug; in load_ksp_mmu()
161 bug: in load_ksp_mmu()
/linux-6.1.9/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…
/linux-6.1.9/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
/linux-6.1.9/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()
/linux-6.1.9/arch/xtensa/mm/
Dtlb.c274 int bug = 0; in check_tlb_sanity() local
279 bug |= check_tlb_entry(w, e, true); in check_tlb_sanity()
282 bug |= check_tlb_entry(w, e, false); in check_tlb_sanity()
283 if (bug & TLB_INSANE) in check_tlb_sanity()
285 if (bug & TLB_SUSPICIOUS) in check_tlb_sanity()
/linux-6.1.9/Documentation/translations/zh_CN/admin-guide/
Dindex.rst33 下面的一组文档，针对的是试图跟踪问题和bug的用户。
41 bug-hunting
42 bug-bisect
Dbug-bisect.rst3 :Original: :doc:`../../../admin-guide/bug-bisect`
20 找到缺陷（bug）并不总是那么容易，不过仍然得去找。如果你找不到它，不要放弃。
/linux-6.1.9/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 …]
/linux-6.1.9/Documentation/translations/zh_TW/admin-guide/
Dindex.rst34 下面的一組文檔，針對的是試圖跟蹤問題和bug的用戶。
41 bug-hunting
42 bug-bisect
/linux-6.1.9/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
/linux-6.1.9/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
/linux-6.1.9/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()
/linux-6.1.9/tools/testing/ktest/
Dktest.pl1703 my $bug = 0;
1726 if (!$bug && !$skip_call_trace) {
1730 $bug = 1;
1740 $bug = 1;
1757 $bug = 1;
1759 return $bug;
2135 my $bug = 0;
2159 if ($bug && defined($stop_after_failure) &&
2209 if (!$bug && !$skip_call_trace) {
2213 $bug = 1;
[all …]

12345678910>>...12