Searched full:bug (Results 1 – 25 of 245) sorted by relevance
12345678910
| /Documentation/admin-guide/cifs/ |
| D | authors.rst | 39 - 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)
58 Test case and Bug Report contributors
60 Thanks to those in the community who have submitted detailed bug reports
|
| /Documentation/filesystems/ |
| D | hpfs.rst | 195 unbalanced trees too :-) but both HPFS and HPFS386 contain bug that it rarely
201 whole created by this driver, it is BUG - let me know about it.
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
[all …]
|
| /Documentation/scsi/ |
| D | ChangeLog.arcmsr | 9 ** 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…
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 64 Bug Reports
67 Any ufs bug report you can send to daniel.pirkl@email.cz or
68 to dushistov@mail.ru (do not send partition tables bug reports).
|
| D | sysfs-rules.rst | 33 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.
|
| D | bug-hunting.rst | 1 Bug hunting
4 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
44 BUG: unable to handle kernel NULL pointer dereference at (null)
51 line is usually required to identify and handle the bug. Along this chapter,
101 Finding the bug's location
104 Reporting a bug works best if you point the location of the bug at the
241 Reporting the bug
244 Once you find where the bug happened, by inspecting its location,
247 In order to report it upstream, you should identify the bug tracker, if any, or
[all …]
|
| D | tainted-kernels.rst | 8 cause might be the event that got the kernel tainted. That's why bug reports
15 notices an internal problem (a 'kernel bug'), a recoverable error
28 BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
92 7 _/D 128 kernel died recently, i.e. there was an OOPS or BUG
96 11 _/I 2048 workaround for bug in platform firmware applied
151 unexpected page flags. This indicates a hardware problem or a kernel bug;
158 7) ``D`` if the kernel has died recently, i.e. there was an OOPS or BUG.
167 11) ``I`` if the kernel is working around a severe bug in the platform
|
| D | index.rst | 42 bug-hunting
43 bug-bisect
|
| /Documentation/process/ |
| D | security-bugs.rst | 7 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
101 delay the bug handling. If a reporter wishes to have a CVE identifier
|
| D | maintainer-kvm-x86.rst | 219 the problem. If both the "what's changing" and "what's the bug" are super
228 If a change fixes a KVM/kernel bug, add a Fixes: tag even if the change doesn't
229 need to be backported to stable kernels, and even if the change fixes a bug in
294 Bug Fixes
297 reproducer for the bug being fixed. In many cases the reproducer is implicit,
303 In general, regression tests are preferred for any bug that is not trivial to
304 hit. E.g. even if the bug was originally found by a fuzzer such as syzkaller,
305 a targeted regression test may be warranted if the bug requires hitting a
309 if a bug is really truly the end of the world before posting a fix without a
317 Do not explicitly reference bug reports, prior versions of a patch/series, etc.
[all …]
|
| D | 5.Posting.rst | 101 bug, rearranges a few structures, and reformats the code, there is a
123 the real bug is elsewhere. Whenever possible, a patch which adds new
167 trying to decide whether a patch should be backported to other kernels, bug
176 needed additional information. If the patch fixes a bug, cite the commit
177 which introduced the bug if possible (and please provide both the commit ID
220 If the URL points to a public bug report being fixed by the patch, use the
225 Some bug trackers have the ability to close issues automatically when a
227 also track such tags and take certain actions. Private bug trackers and
275 the bug was reported in private.
318 - If you are responding to a bug report or a feature request, copy the
[all …]
|
| D | cve.rst | 18 of the :doc:`normal Linux kernel security bug reporting
37 any bug might be exploitable to compromise the security of the kernel,
38 but the possibility of exploitation is often not evident when the bug is
50 :doc:`normal Linux kernel security bug reporting
|
| D | handling-regressions.rst | 24 * Forward or bounce any reports submitted in bug trackers to the list.
36 * When forwarding reports from a bug tracker to the regressions list (see
76 * If a report submitted in a bug tracker hits your Inbox, forward or bounce it
100 * When forwarding a regression reported to a bug tracker, include a paragraph
390 or internal errors (Panic, Oops, BUG(), warning, ...).
433 or a ticket in a bug tracker that are slightly related, but about a different
567 simply because of a kernel bug" is at all relevant.
627 > Kernel had a bug which has been fixed
636 something because we were fixing a bug" is completely insane. We fix
637 tens of bugs every single day, thinking that "fixing a bug" means that
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-maintainer-entry-profile.rst | 71 - **Bug Triager**: Someone who examines incoming bug reports in just
75 The bug triagers should identify themselves with a ``B:`` entry in
95 - **LTS Maintainer**: Someone who backports and tests bug fixes from
124 - Authors of bug fix patches are expected to use fstests[2] to perform
164 - Patchsets implementing bug fixes and further code cleanups should put
165 the bug fixes at the beginning of the series to ease backporting.
169 Bug fixes may be sent at any time, though the release manager may decide to
|
| /Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 89 Bug reports
95 Bug reports should be filled on Freedesktop's bug tracker. Please follow
|
| /Documentation/dev-tools/ |
| D | kasan.rst | 29 is the mode intended to be used as an in-field memory bug detector or as a
104 When it is enabled, KASAN panics the kernel after printing a bug report.
106 By default, KASAN prints a bug report only for the first invalid memory access.
157 allocations. Use the default value for accurate bug detection.
172 BUG: KASAN: slab-out-of-bounds in kmalloc_oob_right+0xa8/0xbc [kasan_test]
242 The report header summarizes what kind of bug happened and what kind of access
246 bug report). Next comes a description of the accessed slab object and the
271 Note that KASAN bug titles (like ``slab-out-of-bounds`` or ``use-after-free``)
272 are best-effort: KASAN prints the most probable bug type based on the limited
273 information it has. The actual type of the bug might be different.
[all …]
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | bug-bisect.rst | 3 :Original: :doc:`../../../admin-guide/bug-bisect`
20 找到缺陷（bug）并不总是那么容易，不过仍然得去找。如果你找不到它，不要放弃。
|
| D | index.rst | 40 bug-hunting
41 bug-bisect
|
| D | tainted-kernels.rst | 20 bug”）、可恢复错误（“kernel oops”）或不可恢复错误（“kernel panic”）时会打印
25 BUG、Oops或Panics消息中的污染标志
31 BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | bug-bisect.rst | 5 :Original: :doc:`../../../admin-guide/bug-bisect`
23 找到缺陷（bug）並不總是那麼容易，不過仍然得去找。如果你找不到它，不要放棄。
|
| D | index.rst | 43 bug-hunting
44 bug-bisect
|
| D | tainted-kernels.rst | 23 bug”）、可恢復錯誤（“kernel oops”）或不可恢復錯誤（“kernel panic”）時會打印
28 BUG、Oops或Panics消息中的污染標誌
34 BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
|
| /Documentation/fb/ |
| D | ep93xx-fb.rst | 123 Screenpage bug
126 At least on the EP9315 there is a silicon bug which causes bit 27 of
128 an unofficial errata for this bug at::
140 avoid this bug. See section 13 of the EP93xx users' guide for details.
|
| /Documentation/fault-injection/ |
| D | provoke-crashes.rst | 37 of the common ones are PANIC, BUG, EXCEPTION, LOOP, and OVERFLOW.
56 # Instead of having a BUG kill your shell, have it kill "cat":
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 76 When reporting a bug related to DC, consider attaching this log before and
77 after you reproduce the bug.
117 attach the log that you obtain from the trace buffer in any bug reports that you
|
12345678910