Home
last modified time | relevance | path

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

12345678910

/Linux-v4.19/lib/
Dbug.c53 static inline unsigned long bug_addr(const struct bug_entry *bug) in bug_addr() argument
56 return bug->bug_addr; in bug_addr()
58 return (unsigned long)bug + bug->bug_addr_disp; 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()
134 struct bug_entry *bug; in find_bug() local
[all …]
/Linux-v4.19/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
32 The goal of the Linux kernel security team is to work with the bug
33 submitter to understand and fix the bug. We prefer to publish the fix as
34 soon as possible, but try to avoid public discussion of the bug itself
37 Publishing the fix may be delayed when the bug or the fix is not yet
41 team working with the bug submitter as well as vendors. However, the
43 timeframe varies from immediate (esp. if it's already publicly known bug)
67 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.
Dbug-hunting.rst4 Kernel bug reports often come with a stack dump like the one below::
41 Kernel's source code where the bug happened. Depending on the severity of
51 line is usually required to identify and handle the bug. Along this chapter,
97 Finding the bug's location
100 Reporting a bug works best if you point the location of the bug at the
233 Reporting the bug
236 Once you find where the bug happened, by inspecting its location,
243 For example, if you find a bug at the gspca's sonixj.c file, you can get
264 Usually, the fastest way to have your bug fixed is to report it to mailing
273 Fixing the bug
[all …]
/Linux-v4.19/Documentation/translations/zh_CN/
DHOWTO221 “没有人知道新内核何时会被发布,因为发布是根据已知bug的情况来决定
323 报告bug
327 户在这个工具中报告找到的所有bug。如何使用内核bugzilla的细节请访问:
331 告可能的内核bug以及需要提供哪些信息来帮助内核开发者们找到问题的根源。
334 利用bug报告
337 练习内核开发技能的最好办法就是修改其他人报告的bug。你不光可以帮助内核变
339 者感受到你的存在。修改bug是赢得其他开发者赞誉的最好办法,因为并不是很多
340 人都喜欢浪费时间去修改别人报告的bug
342 要尝试修改已知的bug,请访问http://bugzilla.kernel.org网址。如果你想获得
343 最新bug的通知,可以订阅bugme-new邮件列表(只有新的bug报告会被寄到这里)
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也会用正确的工具来做这件事,
Dstable_api_nonsense.txt94 找到bug,或者找到更好的实现方式。一旦发现这些,他们就很快会去修改当前的
142 - 其他人会找到驱动中的bug并修复。
Dvolatile-considered-harmful.txt42bug。在正确设计的内核代码中,volatile能带来的仅仅是使事情变慢。
96 bug并且需要对这样的代码额外仔细检查。那些试图使用volatile的开发人员需要退一步想想
/Linux-v4.19/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-v4.19/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-v4.19/arch/mips/kernel/
Dcpu-bugs64.c123 int bug, fix, i; in check_mult_sh() local
145 bug = 0; in check_mult_sh()
148 bug = 1; in check_mult_sh()
150 if (bug == 0) { in check_mult_sh()
/Linux-v4.19/arch/xtensa/mm/
Dtlb.c260 int bug = 0; in check_tlb_sanity() local
265 bug |= check_tlb_entry(w, e, true); in check_tlb_sanity()
268 bug |= check_tlb_entry(w, e, false); in check_tlb_sanity()
269 if (bug & TLB_INSANE) in check_tlb_sanity()
271 if (bug & TLB_SUSPICIOUS) in check_tlb_sanity()
/Linux-v4.19/arch/m68k/include/asm/
Dmmu_context.h124 goto bug; in load_ksp_mmu()
128 goto bug; in load_ksp_mmu()
132 goto bug; in load_ksp_mmu()
137 goto bug; in load_ksp_mmu()
155 bug: in load_ksp_mmu()
/Linux-v4.19/Documentation/filesystems/
Dhpfs.txt180 unbalanced trees too :-) but both HPFS and HPFS386 contain bug that it rarely
199 marks them as short (and writes "minor fs error corrected"). This bug is not in
210 0.91 Fixed bug that caused shooting to memory when write_inode was called on
213 0.93 Fixed bug that locked up the machine when there were too many filenames
217 0.95 Fixed a bug that i_hpfs_parent_dir was not updated when moving files
219 1.91 Fixed a bug that chk_sectors failed when sectors were at the end of disk
221 Fixed a bug that could possibly happen (with very low probability) when
231 1.92 Corrected a bug when sync was called just before closing file
240 Fixed a bug that slowed down alloc and prevented allocating 100% space
241 (this bug was not destructive)
[all …]
Dufs.txt59 Any ufs bug report you can send to daniel.pirkl@email.cz or
60 to dushistov@mail.ru (do not send partition tables bug reports).
/Linux-v4.19/Documentation/filesystems/cifs/
DAUTHORS33 Vince Negri and Dave Stahl (for finding an important caching bug)
44 Aurelien Aptel (for DFS SMB3 work and some key bug fixes)
45 Ronnie Sahlberg (for SMB3 xattr work, bug fixes, and lots of great work on compounding)
47 Sachin Prabhu (many bug fixes, including for reconnect, copy offload and security)
54 Thanks to those in the community who have submitted detailed bug reports
/Linux-v4.19/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()
/Linux-v4.19/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-v4.19/drivers/media/pci/saa7164/
Dsaa7164-bus.c83 int bug = 0; in saa7164_bus_verify() local
86 bug++; in saa7164_bus_verify()
89 bug++; in saa7164_bus_verify()
92 bug++; in saa7164_bus_verify()
95 bug++; in saa7164_bus_verify()
97 if (bug) { in saa7164_bus_verify()
/Linux-v4.19/tools/testing/ktest/
Dktest.pl1595 my $bug = 0;
1618 if (!$bug && !$skip_call_trace) {
1622 $bug = 1;
1632 $bug = 1;
1649 $bug = 1;
1651 return $bug;
2024 my $bug = 0;
2049 if ($bug && defined($stop_after_failure) &&
2099 if (!$bug && !$skip_call_trace) {
2103 $bug = 1;
[all …]
/Linux-v4.19/Documentation/fb/
Dep93xx-fb.txt119 Screenpage bug
122 At least on the EP9315 there is a silicon bug which causes bit 27 of
124 an unofficial errata for this bug at:
135 avoid this bug. See section 13 of the EP93xx users' guide for details.
/Linux-v4.19/fs/affs/
DChanges29 Please direct bug reports to: zippel@linux-m68k.org
40 - several bug fixes found with fsx
172 inode if the fs was not an OFS. This bug only shows
188 - Fixed bug in balloc(): Superblock was not set dirty after
191 - Fixed nasty bug in find_new_zone(): If the current
197 - Fixed bug in add_entry(): When doing a sorted insert,
243 30 characters. (Damn it! This kind of bug
316 - Fixed a nasty bug which didn't allow read-only
/Linux-v4.19/fs/befs/
DChangeLog14 * Oy! Fixed stupid bug that would cause an unresolved symbol error.
46 * Fixed bug in befs_find_brun_indirect() that would result in the wrong
50 * Fixed a longstanding bug in befs_find_key() that would result in it
55 for reporting this serious bug!!!
98 * Fixed stupid bug where specifying the uid or gid mount options as '0'
127 for a while. Thanks to Brent Miszalaski for finding and reporting this bug.
163 clear_inode(). This fixes a potential free twice type bug. Put_inode()
211 * Fixed a bug where the inode and super_block didn't get their blockbits
249 * Fix nasty bug in converting block numbers to struct befs_inode_addr.
253 * Fix bug with reading an empty directory. (btree.c and dir.c)
[all …]

12345678910