Home
last modified time | relevance | path

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

12

/linux-4.4.14/lib/
Dbug.c51 static inline unsigned long bug_addr(const struct bug_entry *bug) in bug_addr() argument
54 return bug->bug_addr; in bug_addr()
56 return (unsigned long)bug + bug->bug_addr_disp; in bug_addr()
67 const struct bug_entry *bug = NULL; in module_find_bug() local
73 bug = mod->bug_table; in module_find_bug()
74 for (i = 0; i < mod->num_bugs; ++i, ++bug) in module_find_bug()
75 if (bugaddr == bug_addr(bug)) in module_find_bug()
78 bug = NULL; in module_find_bug()
82 return bug; in module_find_bug()
132 const struct bug_entry *bug; in find_bug() local
[all …]
DKconfig.kasan46 tristate "Module for testing kasan for bug detection"
DMakefile127 lib-$(CONFIG_GENERIC_BUG) += bug.o
/linux-4.4.14/
DREPORTING-BUGS12 If you've found a bug on a kernel version isn't listed on kernel.org,
15 kernels, and see if you can reproduce the bug on that. It's preferable
16 to reproduce the bug on the latest -rc kernel.
27 increases your chances of getting your bug fixed. Simply posting to the
28 generic linux-kernel mailing list (LKML) may cause your bug report to be
41 bug report. Some maintainers prefer bugs to be reported via bugzilla
45 To find out where to send an emailed bug report, find your subsystem or
47 entries, and send your bug report to the person(s) listed in the "M:"
56 If it is a security bug, please copy the Security Contact listed in the
61 a bug in kernel.org bugzilla and send email to
[all …]
DREADME330 - In all bug-reports, *please* tell what kernel you are talking about,
335 - If the bug results in a message like
DCREDITS727 D: Various security things, bug fixes, and documentation.
1184 D: Miscellaneous bug squisher
1545 D: bug toaster (A1 sauce makes all the difference)
2495 D: General low-level bug fixes, /proc fixes, identd support
2572 D: bug fixes, documentation, minor hackery
2885 D: Some kernel bug fixes
3066 D: Random kernel hacking and bug fixes
3454 D: Miscellaneous bug-fixes
3861 D: Misc bug fixes and GFS2 filesystem development
3889 D: Some bug fixes in the polling printer driver (lp.c)
[all …]
/linux-4.4.14/Documentation/
DSecurityBugs2 like to know when a security bug is found so that it can be fixed and
10 who will help verify the bug report and develop and release a fix.
14 As it is with any bug, the more information provided the easier it
23 bug submitter to bug resolution as well as disclosure. We prefer
24 to fully disclose the bug as soon as possible. It is reasonable to
25 delay disclosure when the bug or the fix is not yet fully understood,
29 bug submitter as well as vendors. However, the kernel security team
DBUG-HUNTING11 - Finding patch that caused a bug
14 - Fixing the bug
20 not confident in doing that please report the bug to your distribution vendor
27 Before you submit a bug report read REPORTING-BUGS.
35 Finding patch that caused a bug
43 Using the provided tools with git makes finding bugs easy provided the bug is
56 This is how to track down a bug if you know nothing about kernel hacking.
61 . A reproducible bug - it has to happen predictably (sorry)
69 introduced the bug. I.e., suppose 1.3.28 didn't have the bug, but
73 . You'll narrow it down to the kernel that introduced the bug. You
[all …]
Dsysfs-rules.txt32 system configuration bug you should not try to solve. For test cases,
57 is a bug in the application
76 bug in the application
82 like the "device"-link, is a bug in the application
122 /sys/block and /sys/class/block are not interchangeable is a bug in
130 a bug in the application.
140 a device in /sys/devices/ is a bug in the application.
141 Accessing /sys/class/net/eth0/device is a bug in the application.
150 real child device directories in the /sys/devices tree is a bug in
163 access the chain of parents is a bug in the application.
Dsvga.txt166 you can switch it off and report as a bug.
206 In either case, please send me a bug report containing what _exactly_
207 happens and how do the configuration switches affect the behaviour of the bug.
216 contains the most common video BIOS bug called "incorrect vertical display
239 VESA modes work now). Display end bug workaround supported.
249 2.5 (19-Mar-96) Fixed a VESA mode scanning bug introduced in 2.4.
Dlockup-watchdogs.txt8 A 'softlockup' is defined as a bug that causes the kernel to loop in
18 A 'hardlockup' is defined as a bug that causes the CPU to loop in
DSubmittingPatches109 Describe your problem. Whether your patch is a one-line bug fix or
160 If the patch fixes a logged bug entry, refer to that bug entry by
168 bug, summarize the relevant points of the discussion that led to the
187 If your patch fixes a bug in a specific commit, e.g. you found an issue using
206 For example, if your changes include both bug fixes and performance
292 If you have a patch that fixes an exploitable security bug, send that patch
297 Patches that fix a severe bug in a released kernel should be directed
544 the bug was reported in private, then ask for permission first before using the
594 is used to make it easy to determine where a bug originated, which can help
595 review a bug fix. This tag also assists the stable kernel team in determining
[all …]
Dvolatile-considered-harmful.txt22 almost certainly a bug in the code somewhere. In properly-written kernel
96 result, the use of volatile is likely to be seen as a bug and will bring
Doops-tracing.txt69 That's the easy way to find the problem, at least if the bug-report is
77 The other thing to do is disassemble the "Code:" part of the bug report:
106 make fs/buffer.s # or whatever file the bug happened in
263 12: 'I' if the kernel is working around a severe bug in the platform
Dkasan.txt31 For better bug detection and nicer reporting, enable CONFIG_STACKTRACE.
120 The header of the report discribe what kind of bug happened and what kind of
DSAK.txt62 So `gpm' will be killed by SAK. This is a bug in gpm. It should
DHOWTO262 released according to perceived bug status, not according to a
342 template for how to report a possible kernel bug, and details what kind
347 Managing bug reports
357 To work in the already reported bug reports, go to http://bugzilla.kernel.org.
358 If you want to be advised of the future bug reports, you can subscribe to the
359 bugme-new mailing list (only new bug reports are mailed here) or to the
DIntel-IOMMU.txt59 If this fixes anything, please ensure you file a bug reporting the problem.
Dhwspinlock.txt144 Doing so is considered a bug (there is no protection against this).
152 Doing so is considered a bug (there is no protection against this).
Dxz.txt109 Before reporting a bug, please check that it's not fixed already
DSubmittingDrivers85 you because you get patches not bug reports. If you submit a
Dstable_kernel_rules.txt9 - It must fix a real bug that bothers people (not a, "This could be a
Dlzo.txt14 for future bug reports.
DCodingStyle433 A common type of bug to be aware of it "one err bugs" which look like this:
440 The bug in this code is that on some exit paths "foo" is NULL. Normally the
611 have a reference count on it, you almost certainly have a bug.
728 introduces an opportunity for a bug when the pointer variable type is changed
Dunaligned-memory-access.txt60 resulting in a subtle code bug that is hard to detect!
DChanges16 encountered a bug! If you're unsure what version you're currently
Demail-clients.txt181 $ mutt -H 0001-some-bug-fix.patch
Dremoteproc.txt47 to rproc_shutdown(). Calling rproc_shutdown() redundantly is a bug.
/linux-4.4.14/Documentation/zh_CN/
DHOWTO225 “没有人知道新内核何时会被发布，因为发布是根据已知bug的情况来决定
327 报告bug
331 户在这个工具中报告找到的所有bug。如何使用内核bugzilla的细节请访问：
335 告可能的内核bug以及需要提供哪些信息来帮助内核开发者们找到问题的根源。
338 利用bug报告
341 练习内核开发技能的最好办法就是修改其他人报告的bug。你不光可以帮助内核变
343 者感受到你的存在。修改bug是赢得其他开发者赞誉的最好办法，因为并不是很多
344 人都喜欢浪费时间去修改别人报告的bug。
346 要尝试修改已知的bug，请访问http://bugzilla.kernel.org网址。如果你想获得
347 最新bug的通知，可以订阅bugme-new邮件列表（只有新的bug报告会被寄到这里）
Dstable_api_nonsense.txt94 找到bug，或者找到更好的实现方式。一旦发现这些，他们就很快会去修改当前的
142 - 其他人会找到驱动中的bug并修复。
Dvolatile-considered-harmful.txt42 个bug。在正确设计的内核代码中，volatile能带来的仅仅是使事情变慢。
96 bug并且需要对这样的代码额外仔细检查。那些试图使用volatile的开发人员需要退一步想想
DSubmittingPatches89 序”，“修正了某驱动程序的bug”，或者“这个补丁包含了某子系统的修改，请
99 例如，如果你的改动里同时有bug修正和性能优化，那么把这些改动拆分到两个或
127 那些修正bug，“显而易见”的修改或者是类似的只需要很少讨论的补丁可以直接
DCodingStyle496 里几乎肯定是一个bug。
584 入bug。有可能指针变量类型被改变时，而对应的传递给内存分配函数的sizeof的结果不变。
616 混合使用这两种表达方式是难于发现的bug的来源。如果C语言本身严格区分整形和布尔型变
617 量，那么编译器就能够帮我们发现这些错误……不过C语言不区分。为了避免产生这种bug，请
Dstable_kernel_rules.txt33 - 必须修正了一个给大家带来麻烦的真正的bug（不是“这也许是一个问题...”
Doops-tracing.txt77 那是发现问题的简单办法，至少如果bug报告做的好的情况下（象这个一样-运行ksymoops
82 另一件要做的事是反汇编bug报告的“Code”部分：ksymoops也会用正确的工具来做这件事，
DSubmittingDrivers97 会直接收到修复的补丁而不是 bug 报告。如果你提交一个试图
Demail-clients.txt117 自己的窗口之下察看，那时没有选项可以保存邮件--已经有一个这样的bug被汇报到了kmail的bugzilla
/linux-4.4.14/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…
Din2000.txt26 Fixed a bug that caused incorrect SCSI status bytes to be
28 means that CDROM changers work now! Fixed a bug in the
38 Fixed a bug in the code that sets the transfer direction
72 Fixed a well-hidden bug in the adaptive-disconnect code
80 1.25 had a nasty bug that bit people with swap partitions
105 There was a bug in the synchronous transfer code. Only
Ddpti.txt42 * Fixed bug causing system to hang under extreme load with
54 * Fixed pointer bug in bus reset routine
DChangeLog.1992-1997135 throughout and fixed bug interrupt routine which resulted in shifted
137 Memory management bug seems to have disappeared ==> increasing
176 * eata.c: Update to version 2.0. Fixed bug preventing media
186 * u14-34f.c: Update to version 2.0. Fixed same bug as in
252 Continuing modularization. Less crashes because of the bug in the
377 * eata_dma: Update to version 2.10i. Remove bug in the registration
432 * ultrastor.c: Fix bug in call to ultrastor_interrupt (wrong #args).
1007 * sd.c: Fix bug when we were deleting the wrong entry if we
1104 * seagate.c: Fix bug. [Drew]
1136 * seagate.c: Fix bug that resulted in lockups with some devices.
[all …]
Dadvansys.txt199 Thomas E Zerucha <zerucha@shell.portal.com> pointed out a bug
215 Ken Mort <ken@mort.net> reported a DEBUG compile bug fixed
235 board support and fixed a bug in AscGetEEPConfig().
DChangeLog.lpfc225 * Fix double locking bug in the error handling part of
298 * Workaround firmware bug for IOERR_RCV_BUFFER_WAITING on ELS
336 * VPD info bug fix.
355 freed (after nodev tmo). This bug was causing i/o received in
366 * Fixed bug for handling RSCN type 3. Terminate RSCN mode
372 * Fixed potential discovery bug, nlp list corrutpion fix potential
388 * Fixed bug introduced when discovery thread implementation was
475 * Fix for Scsi device scan bug reported on SourceForge. Driver
501 * Fix an obvious typo/bug: kfree was used to free lpfc_scsi_buf
538 * Fixed discovery bug: plogi cmpl uses ndlp after its freed.
[all …]
DChangeLog.ncr53c8xx187 - Fix some oooold bug that hangs the bus if a device rejects a
277 SCSI specs, this is a device firmware bug. This has been worked
322 This also fixes a bug triggered when disabling tagged command
383 - Fix something that looks like an old bug in the nego SIR
405 - Fix a bug when QUEUE FULL is returned and no commands are
DNinjaSCSI.txt118 Please send me some reports(bug reports etc..) of this software.
DChangeLog.megaraid21 1. Fixed a bug in megaraid_init_mbox().
144 1. Fixed a bug in megaraid_reset_handler().
373 i. Fix a bug in kioc's dma buffer deallocation
517 vi. Fix bug in the management module, which causes a system lockup when the
Daacraid.txt134 …dded some new product ids for upcoming hbas. Performance tuning, card failover and bug mitigations.
DChangeLog.sym53c8xx_224 - A tiny bug in the dma memory freeing path has been fixed.
DChangeLog.sym53c8xx176 - Fix an old bug that only affected 896 rev. 1 when driver
226 - Fix in a tiny 'printk' bug that may oops in case of extended
270 - Fix some bug in the fully untested MDP handling:) and share
394 - Fix some oooold bug that hangs the bus if a device rejects a
Dscsi-changer.txt77 doesn't, it is a bug. Either within the driver or within the firmware
Dosd.txt181 Any problems, questions, bug reports, lonely OSD nights, please email:
Dncr53c8xx.txt1207 this chip bug, unlike i486 systems that use a 4 DWORDS cache line size.
1213 Not using Write And Invalidate obviously gets rid of this chip bug, and so
1217 addressing logic when the DATA IN phase is entered and so prevents the bug
1224 boundary (Pentium Cache Line Size), and so is immune to this chip bug, at
1226 But the conditions of this bug can be met when a SCSI read command is
1257 be sure I will receive it. Obviously, a bug in the driver code is
/linux-4.4.14/arch/sh/kernel/
Dtraps.c86 const struct bug_entry *bug; in handle_BUG() local
93 bug = find_bug(bugaddr); in handle_BUG()
96 if (bug->flags & BUGFLAG_UNWINDER) in handle_BUG()
144 BUILD_TRAP_HANDLER(bug) in BUILD_TRAP_HANDLER() argument
/linux-4.4.14/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-4.4.14/arch/xtensa/mm/
Dtlb.c262 int bug = 0; in check_tlb_sanity() local
267 bug |= check_tlb_entry(w, e, true); in check_tlb_sanity()
270 bug |= check_tlb_entry(w, e, false); in check_tlb_sanity()
271 if (bug & TLB_INSANE) in check_tlb_sanity()
273 if (bug & TLB_SUSPICIOUS) in check_tlb_sanity()
/linux-4.4.14/arch/m68k/include/asm/
Dmmu_context.h123 goto bug; in load_ksp_mmu()
127 goto bug; in load_ksp_mmu()
131 goto bug; in load_ksp_mmu()
136 goto bug; in load_ksp_mmu()
154 bug: in load_ksp_mmu()
/linux-4.4.14/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).
Dcramfs.txt42 == 4096. At least the latter of these is a bug, but it hasn't been
Dbtrfs.txt117 "bug" - BUG() on a fatal error. This is the default.
Daffs.txt14 a bug has been fixed so that accented ("international") letters
Dvfat.txt200 If you have trouble with the VFAT filesystem, mail bug reports to
/linux-4.4.14/include/linux/
Dbug.h91 static inline int is_warning_bug(const struct bug_entry *bug) in is_warning_bug() argument
93 return bug->flags & BUGFLAG_WARNING; in is_warning_bug()
/linux-4.4.14/arch/ia64/
DKconfig.debug43 bool "Turn on compare-and-exchange bug checking (slow!)"
46 Selecting this option turns on bug checking for the IA-64
55 Selecting this option turns on bug checking for the IA-64 irq_save
/linux-4.4.14/drivers/media/pci/saa7164/
Dsaa7164-bus.c87 int bug = 0; in saa7164_bus_verify() local
90 bug++; in saa7164_bus_verify()
93 bug++; in saa7164_bus_verify()
96 bug++; in saa7164_bus_verify()
99 bug++; in saa7164_bus_verify()
101 if (bug) { in saa7164_bus_verify()
/linux-4.4.14/tools/testing/ktest/
Dktest.pl1529 my $bug = 0;
1552 if (!$bug && !$skip_call_trace) {
1556 $bug = 1;
1566 $bug = 1;
1583 $bug = 1;
1585 return $bug;
1925 my $bug = 0;
1950 if ($bug && defined($stop_after_failure) &&
2000 if (!$bug && !$skip_call_trace) {
2004 $bug = 1;
[all …]
/linux-4.4.14/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.
Dfbcon.txt39 GOTCHA: A common bug report is enabling the framebuffer without enabling the
/linux-4.4.14/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-4.4.14/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 …]
/linux-4.4.14/include/asm-generic/
Dbug.h9 #define BUG_GET_TAINT(bug) ((bug)->flags >> 8) argument
/linux-4.4.14/arch/sh/include/asm/
Dtraps.h14 BUILD_TRAP_HANDLER(bug);
/linux-4.4.14/arch/m68k/fpsp040/
Dbugfix.S177 | Test for cu_savepc equal to zero. If not, this is not a bug
182 beq fix_done |if zero, this is not bug #1238
189 | exit, it is not the bug case.
206 | bug condition. Otherwise, exit.
354 bne fix_done |if not, it is not bug 1238
358 | go and fix the bug condition. Otherwise, exit.
489 | bug #1238, or if the fix is completed, and exit.
Dskeleton.S88 | Code following the 'inex' label is to handle bug #1232. In this
89 | bug, if an E1 snan, ovfl, or unfl occurred, and the process was
132 | We do not have the bug 1232 case. Clean up the stack and call
Dgen_except.S321 | fix the bug with the nmnexc bits in cases in which they
/linux-4.4.14/sound/oss/
DREADME.FIRST4 forums for bug reporting.
DCHANGELOG21 - Fixed the famous Quake delay bug.
47 - Fixed a bug in handling of non-fragment sized writes in 16 bit/stereo mode
62 - Fixed a bug in handling of full duplex cards in write only mode. This has
133 - Fixed bug in handling of uninitialized instruments with GUS.
141 - Fixed the above bug in proper way and in proper place. Many thanks
226 - Some important bug fixes.
264 - Minor and major bug fixes
319 - Fixed bug which made it impossible to make long recordings to disk.
340 - Fixed a bug in the compute_and_set_volume in gus_wave.c
/linux-4.4.14/net/sctp/
Dsm_statetable.c60 static const sctp_sm_table_entry_t bug = { variable
72 rtn = &bug; \
98 return &bug; in sctp_sm_lookup_event()
909 return &bug; in sctp_chunk_event_lookup()
/linux-4.4.14/Documentation/i2c/busses/
Di2c-sis96x45 via the linux-i2c mailing list: <linux-i2c@vger.kernel.org>. Please send bug
60 - design hints and bug fixes
Di2c-sis63055 - bug fixes
Di2c-piix4104 which can easily get corrupted due to a state machine bug. These are mostly
/linux-4.4.14/arch/arm/boot/dts/
Dimx31-bug.dts17 compatible = "buglabs,imx31-bug", "fsl,imx31";
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-platform-at9110 Due to a chip bug (errata 50.2.6.3 & 50.3.5.3 in
Dsysfs-bus-pci294 a firmware bug to the system vendor. Writing to this file
/linux-4.4.14/Documentation/filesystems/cifs/
DAUTHORS33 Vince Negri and Dave Stahl (for finding an important caching bug)
47 Thanks to those in the community who have submitted detailed bug reports
DCHANGES70 Fix "redzone overwritten" bug in cifs_put_tcon (CIFSTcon may allocate too
120 Fix bug in rewinding readdir directory searches. Add nodfs mount option.
219 copies caused by writepages page i/o completion bug.
612 Fix caching data integrity bug when extending file size especially when no
660 Fix byte range locking bug (endian problem) causing bad offset and
800 Fix truncate bug (set file size) that could cause hangs e.g. running fsx
809 Windows bug. Add /proc/fs/cifs/LookupCacheEnable which
886 the iozone benchmark to fail on the fwrite test. Fix bug mounting two different
916 Fix bigendian bug in order of time conversion. Merge 2.5 to 2.4 version. Formatting cleanup.
1015 Rewrite of readdir code to fix bug. Various fixes for bigendian machines.
[all …]
DTODO82 current bug list. Also check http://bugzilla.kernel.org (Product = File System, Component = CIFS)
/linux-4.4.14/Documentation/hwmon/
Dmax161912 Oleksij Rempel <bug-track@fisher-privat.net>,
Dlm85108 Devices has confirmed this "bug". The ADT7463 is reported to work as
192 NOTE: It has been reported that there is a bug in the LM85 that causes the flag
Dsubmitting-patches45 * Never mix bug fixes, cleanup, and functional enhancements in a single patch.
/linux-4.4.14/arch/um/include/asm/
DKbuild2 generic-y += bug.h
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-floppy.1996-20027 * Ver 0.3 Dec 2 96 Fixed error recovery bug.
18 * Ver 0.9 Jul 4 99 Fix a bug which might have caused the number of
DChangeLog.ide-tape.1995-200257 * Few potential bug fixes (Again, suggested by Mark)
106 * Ver 1.3 Feb 9 96 Fixed pipelined read mode bug which prevented the
126 * Fixed nasty null dereferencing bug.
128 * Fixed end of media bug.
137 * Some error recovery bug fixes.
DChangeLog.ide-cd.1994-200433 * Fix a bug in handling the sector cache which
151 * 4.10 Jan 24, 1998 -- fixed a bug so now changers can change to a new
162 * -- Fixed a stupid bug which egcs was kind enough to
166 * 4.12 Mar 29, 1998 -- Fixed bug in CDROM_SELECT_SPEED so write speed is
Dide.txt205 a case please report it as a bug instead) use "ignore_cable" kernel parameter:
/linux-4.4.14/arch/xtensa/include/asm/
DKbuild2 generic-y += bug.h
/linux-4.4.14/arch/x86/um/
DMakefile11 obj-y = bug.o bugs_$(BITS).o delay.o fault.o ksyms.o ldt.o \
/linux-4.4.14/Documentation/devicetree/bindings/net/can/
Dgrcan.txt25 a bug workaround is activated.
/linux-4.4.14/arch/tile/include/asm/
DKbuild4 generic-y += bug.h
/linux-4.4.14/scripts/coccinelle/misc/
Dbugon.cocci60 …the condition has no side effects (see conditional BUG_ON definition in include/asm-generic/bug.h)"
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.freeze5 It might be a bttv driver bug. It also might be bad hardware. It also
16 bug. It is very helpful if you can tell where exactly it broke
DREADME.quirks2 Below is what the bt878 data book says about the PCI bug compatibility
DInsmod-options21 vsfx=0/1 yet another chipset bug compatibility bit
/linux-4.4.14/scripts/genksyms/
Dkeywords.hash.c_shipped28 …d tables don't work with this execution character set. Please report a bug to <bug-gnu-gperf@gnu.o…
/linux-4.4.14/Documentation/networking/
Dnetdev-FAQ.txt87 A: Firstly, think whether you have a bug fix or new "next-like" content.
93 bug-fix net content. If you don't use git, then note the only magic in
162 bug was introduced. If you do that properly, then the commit will
193 Q: I found a bug that might have possible security implications or similar.
215 doing so. If your change is a bug-fix, make sure your commit log
Dcxgb.txt270 Corruption" bug identified by AMD while using a 133Mhz PCI-X card on the
278 recommends the first option for best performance with this bug:
289 details with this bug and workarounds suggested by AMD.
294 and duplicate the problem before submitting a bug or asking for support.
Dfore200e.txt63 Feedback is welcome. Please send success stories/bug reports/
Dspider_net.txt111 The RX RAM full bug/feature
123 a certain bug/feature is triggered that has to be specially handled.
169 This bug/feature is worked around with the spider_net_resync_head_ptr()
Dnetdevices.txt84 Usually a bug, means queue start/stop flow control is broken in
Dgeneric-hdlc.txt128 Attaching this info to bug reports would be helpful. Anyway, let me know
Ddecnet.txt165 6) How to send a bug report
167 If you've found a bug and want to report it, then there are several things
Dnetconsole.txt7 Please send bug reports to Matt Mackall <mpm@selenic.com>
D6pack.txt169 If you encounter a bug or if you have a question or suggestion concerning the
Drds.txt232 "back-pressure" is considered a bug.
/linux-4.4.14/Documentation/sound/alsa/
DProcfile.txt212 If it's really a bug, report it with the following information:
232 The ALSA bug-tracking system is found at:
234 https://bugtrack.alsa-project.org/alsa-bug/
Dpowersave.txt35 don't report extra bug reports unless you have a fix patch ;-)
DHD-Audio.txt218 Before making a bug report, double-check whether the mixer is set up
233 functionality. If none of the available models works, send a bug
234 report. See the bug report section for details.
257 Thus, before submitting a bug report, make sure that you set up the
273 and the recorded sound contains a certain DC-offset. This is no bug
673 to send a bug report to the developers. Give the following in your
674 bug report:
685 Send a bug report either the followings:
710 on alsa-project.org. But, if you send a bug report, it'd be better to
DREADME.maya4442 …ti track") in 'alsamixer' do not seem to react to signals in (if this is a bug, it would probably …
DCMIPCI.txt254 output of this proc file together with the bug report.
/linux-4.4.14/Documentation/development-process/
D5.Posting95 bug, rearranges a few structures, and reformats the code, there is a
117 the real bug is elsewhere. Whenever possible, a patch which adds new
158 trying to decide whether a patch should be backported to other kernels, bug
167 needed additional information. If the patch fixes a bug, cite the commit
168 which introduced the bug if possible (and please provide both the commit ID
267 - If you are responding to a bug report or a feature request, copy the
273 - If you are fixing a bug, think about whether the fix should go into the
D6.Followthrough150 where there are testers, there will be bug reports.
152 The worst sort of bug reports are regressions. If your patch causes a
164 release is as solid as possible. So, please, answer bug reports, and fix
169 And don't forget that there are other milestones which may also create bug
D7.AdvancedTopics67 say, or which has some other sort of obvious bug) can be fixed in place or
/linux-4.4.14/arch/powerpc/platforms/8xx/
DKconfig136 This bug can cause incorrect code execution under certain
139 to disable it if you have worked around the bug in the compiler
/linux-4.4.14/mm/
Dmmap.c380 int i = 0, j, bug = 0; in browse_rb() local
390 bug = 1; in browse_rb()
395 bug = 1; in browse_rb()
400 bug = 1; in browse_rb()
406 bug = 1; in browse_rb()
418 bug = 1; in browse_rb()
420 return bug ? -1 : i; in browse_rb()
438 int bug = 0; in validate_mm() local
460 bug = 1; in validate_mm()
465 bug = 1; in validate_mm()
[all …]
/linux-4.4.14/arch/arm64/include/asm/
DKbuild3 generic-y += bug.h
/linux-4.4.14/Documentation/devicetree/bindings/fuse/
Dnvidia,tegra20-fuse.txt11 due to a hardware bug. Tegra20 also lacks certain information which is
/linux-4.4.14/drivers/md/
Ddm-bufio.c1858 int bug = 0; in dm_bufio_exit() local
1873 bug = 1; in dm_bufio_exit()
1879 bug = 1; in dm_bufio_exit()
1885 bug = 1; in dm_bufio_exit()
1891 bug = 1; in dm_bufio_exit()
1894 if (bug) in dm_bufio_exit()
/linux-4.4.14/arch/hexagon/include/asm/
DKbuild6 generic-y += bug.h
/linux-4.4.14/drivers/scsi/osd/
DKconfig47 dmesg. Enable this if you found a bug and you want to help us
/linux-4.4.14/arch/mn10300/kernel/
Dgdb-stub.c1232 const struct bug_entry *bug; in gdbstub() local
1234 bug = find_bug(regs->pc); in gdbstub()
1235 if (bug) in gdbstub()
1244 regs->pc, bug->file, bug->line); in gdbstub()
/linux-4.4.14/arch/nios2/include/asm/
DKbuild6 generic-y += bug.h
/linux-4.4.14/arch/openrisc/include/asm/
DKbuild8 generic-y += bug.h
/linux-4.4.14/Documentation/scheduler/
Dcompletion.txt77 most likely a bug as it re-initializes the queue to an empty queue and
219 done element. Calling complete_all() multiple times is a bug though. Both
225 probably are a design bug.
/linux-4.4.14/drivers/md/bcache/
Dbset.c75 goto bug; in __bch_check_keys()
82 goto bug; in __bch_check_keys()
89 goto bug; in __bch_check_keys()
96 goto bug; in __bch_check_keys()
99 bug: in __bch_check_keys()
/linux-4.4.14/drivers/staging/speakup/
DTODO36 This bug happens regularly, but no one has been able to find a situation
/linux-4.4.14/scripts/kconfig/
Dzconf.hash.c_shipped28 …d tables don't work with this execution character set. Please report a bug to <bug-gnu-gperf@gnu.o…
/linux-4.4.14/Documentation/usb/
Derror-codes.txt32 of urb. (treat as a host controller bug.)
93 (That is, if drivers see this it's a bug.)
Dgadget_multi.txt76 out for this bug.
/linux-4.4.14/Documentation/sound/oss/
DSoundblaster25 Consider it a bug if this option is needed, and send in a
DIntroduction54 forums for bug reporting.
/linux-4.4.14/Documentation/dvb/
DREADME.dvb-usb72 2004-12-29 - after several days of struggling around bug of no returning URBs fixed.
183 The bug, where the TS is distorted by a heavy usage of the device is gone
203 Bernd Wagner for helping with huge bug reports and discussions.
Dbt8xx.txt57 For bug reports please send in a complete log with verbose=4 activated.
Dfaq.txt5 It's not a bug, it's a feature. Because the frontends have
/linux-4.4.14/tools/testing/selftests/futex/
DREADME24 the individual tests on mailing list discussions and bug reports.
/linux-4.4.14/arch/arm/mach-imx/
DMakefile65 obj-$(CONFIG_MACH_BUG) += mach-bug.o
/linux-4.4.14/arch/powerpc/xmon/
Dxmon.c1465 const struct bug_entry *bug; in print_bug_trap() local
1473 bug = find_bug(regs->nip); in print_bug_trap()
1474 if (bug == NULL) in print_bug_trap()
1476 if (is_warning_bug(bug)) in print_bug_trap()
1481 bug->file, bug->line); in print_bug_trap()
1483 printf("kernel BUG at %p!\n", (void *)bug->bug_addr); in print_bug_trap()
/linux-4.4.14/arch/x86/
DMakefile_32.cpu57 # Work around to a bug with asm goto with first implementations of it
DKconfig.cpu87 against the f00f bug found in earlier Pentiums.
328 enabling this: there are few systems, and an unlikely bug.
DKconfig2015 The bug was introduced by f866314b89d56845f55e6f365e18b31ec978ec3a
2018 the only released version with the bug, but OpenSUSE 9
2021 The symptom of the bug is that everything crashes on startup, saying:
2026 This works around the glibc bug but hurts performance.
2245 series notebooks, it is necessary to say Y because of a BIOS bug.
/linux-4.4.14/Documentation/thermal/
Dnouveau_thermal81 Bug reports should be filled on Freedesktop's bug tracker. Please follow
/linux-4.4.14/fs/overlayfs/
Dsuper.c286 goto bug; in ovl_d_real()
295 goto bug; in ovl_d_real()
304 bug: in ovl_d_real()
/linux-4.4.14/arch/openrisc/
DKconfig142 bool "Check for possible ESR exception bug"
/linux-4.4.14/tools/perf/
DMANIFEST30 tools/include/asm/bug.h
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-api.txt24 the system. If userspace fails (RAM error, kernel bug, whatever), the
47 good idea, since if there is a bug in the watchdog daemon and it
/linux-4.4.14/Documentation/arm/
DREADME51 When sending bug reports, please ensure that they contain all relevant
139 Known bug: Drive data errors can cause a hang; including cases where
/linux-4.4.14/drivers/video/fbdev/omap2/dss/
DKconfig129 reset. The reason for the bug is unclear, and it's also unclear
/linux-4.4.14/fs/reiserfs/
DKconfig40 effect on end users. If you are on the verge of sending in a bug
DREADME50 Send bug reports to yura@namesys.botik.ru.
/linux-4.4.14/Documentation/acpi/
Dinitrd_table_override.txt32 Complain to your platform/BIOS vendor if you find a bug which is so sever
/linux-4.4.14/Documentation/arm/nwfpe/
DREADME43 which instruction contains the bug. Small programs illustrating a specific
DREADME.FPE143 have a bug in them that prevents the module from generating a SIGFPE. This
/linux-4.4.14/Documentation/w1/masters/
Dds249066 host did not explain the problem. My guess is a bug in either qemu
/linux-4.4.14/Documentation/blockdev/
Dfloppy.txt228 If you have a question or a bug report about the floppy driver, mail
235 Be sure to read the FAQ before mailing/posting any bug reports!
Dparide.txt391 include that with your bug report. You can submit a bug report in one
DREADME.DAC96038 Driver bug reports should be sent via electronic mail to "lnz@dandelion.com".
39 Please include with the bug report the complete configuration messages reported
/linux-4.4.14/arch/arm/nwfpe/
DChangeLog90 * fpa11_cpdt.c - fixed bug in storeExtended (typeExtended changed to
/linux-4.4.14/tools/usb/usbip/
DINSTALL197 an Autoconf bug. Until the bug is fixed you can use this workaround:
/linux-4.4.14/arch/arc/kernel/
Dentry.S65 ; Workaround for bug 94179 (STAR ):
/linux-4.4.14/drivers/net/wireless/ath/carl9170/
Ddebug.c678 __DEBUGFS_DECLARE_RW_FILE(bug, 400, CARL9170_STOPPED);
869 DEBUGFS_ADD(bug); in carl9170_debugfs_register()
/linux-4.4.14/arch/powerpc/boot/dts/
Dvirtex440-ml510.dts5 * The reference design contains a bug which prevent PCI DMA from working
6 * properly. A description of the bug is given in the plbv46_pci section. It
/linux-4.4.14/Documentation/locking/
Dlocktorture.txt127 -only- be positive if there is a bug in the locking primitive's
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt149 frame counter. With a spec laywer hat on this isn't a bug since timeouts can
187 drivers it's a userspace bug to submit the same object twice in the same
/linux-4.4.14/tools/perf/config/
Dutilities.mak70 # (The bash shell has a bug where `{gsub(...),...}' is
/linux-4.4.14/Documentation/video4linux/
DZoran475 (<laurent.pinchart@skynet.be> and <rbultje@ronald.bitfreak.net>). For bug
477 individually. For user questions (i.e. bug reports or how-to questions), send
482 For bug reports, be sure to include all the information as described in
/linux-4.4.14/Documentation/crypto/
Dapi-intro.txt122 Send bug reports to:
/linux-4.4.14/fs/cramfs/
DREADME99 This discrepancy is a bug, though it's not clear which should be
/linux-4.4.14/Documentation/laptops/
Dasus-laptop.txt66 bug report to do, please include the output of this entry.
/linux-4.4.14/arch/powerpc/platforms/44x/
DKconfig356 This option enables a work around for an icache bug on 476
/linux-4.4.14/Documentation/cpu-freq/
Dpcc-cpufreq.txt146 | -- this will increase with bug fixes/enhancements to the driver
/linux-4.4.14/arch/m32r/
DKconfig299 bool "Workaround code for the M32700 TS1 chip's bug"
/linux-4.4.14/Documentation/isdn/
DsyncPPP.FAQ211 Could be a bug in the ipppd.
DREADME.sc280 referenced... segv. The bug has been fixed around line 63-68 of event.c.
DREADME.gigaset363 use one of the forums, bug trackers, or mailing lists on
/linux-4.4.14/firmware/keyspan_pda/
Dkeyspan_pda.S569 ;; web site, but from the example code it looks like this bug causes
576 ;; now I will just live with the bug.
Dxircom_pgs.S607 ;; web site, but from the example code it looks like this bug causes
614 ;; now I will just live with the bug.
/linux-4.4.14/arch/arm/kernel/
Dentry-armv.S582 * for the ARM6/ARM7 SWI bug.
/linux-4.4.14/drivers/mtd/devices/
DKconfig37 suspect a possible hardware or driver bug. If unsure say N.
/linux-4.4.14/Documentation/cdrom/
Dide-cd321 - There was a bug in the version of the driver in 1.2.x kernels
328 bug.
/linux-4.4.14/block/partitions/
DKconfig206 report a bug.
/linux-4.4.14/arch/powerpc/platforms/
DKconfig166 that have a bug that causes some interrupt source information
/linux-4.4.14/scripts/
DKbuild.include289 # This is a good hint that there is a bug in the kbuild file
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt322 bug fixes and enhancements that have gone into subsequent releases.
2338 hosts, where there's a bug which causes signals to UML to be lost,
2446 mconsole loop and all others will continue as normal. This is a bug,
2503 Not every bug is evident in the currently running process. Sometimes,
3838 are diagnostic of this problem. This is a reiserfs bug which causes a
3877 another bug, but that one is fairly hard to reproduce.
3893 This is a syslogd bug. There's a race between a parent process
4301 o lots of bug reports
4387 o Lots of testing and bug reports
/linux-4.4.14/arch/tile/
DKconfig109 # to sparsemem (Tilera bug 7996).
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dhead.S53 ;; whether the bug is present, some constants would then have to
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt246 irrecoverably, either due to a bug or a media error. The following conditions
/linux-4.4.14/Documentation/RCU/
Dtrace.txt224 "?" Unknown value, indicates a bug.
476 "?" Unknown value, indicates a bug.
Drcu_dereference.txt173 of such an RCU usage bug is shown in the section titled
Dstallwarn.txt243 o A bug in the RCU implementation.
/linux-4.4.14/Documentation/vm/
Dslub.txt8 an impact on overall system performance which may make a bug more
/linux-4.4.14/Documentation/powerpc/
Deeh-pci-error-recovery.txt43 The most common software bug, is one that causes the device to

12