Lines Matching full:bug
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.
160 allocations. Use the default value for accurate bug detection.
175 BUG: KASAN: slab-out-of-bounds in kmalloc_oob_right+0xa8/0xbc [kasan_test]
245 The report header summarizes what kind of bug happened and what kind of access
249 bug report). Next comes a description of the accessed slab object and the
274 Note that KASAN bug titles (like ``slab-out-of-bounds`` or ``use-after-free``)
275 are best-effort: KASAN prints the most probable bug type based on the limited
276 information it has. The actual type of the bug might be different.
289 the bug and correlate the error with other system events, at the cost of using
360 this memory. In case of a tag mismatch, Software Tag-Based KASAN prints a bug
365 memory checks inline). With outline instrumentation mode, a bug report is
368 dedicated ``brk`` handler is used to print bug reports.
402 Hardware Tag-Based KASAN only reports the first found bug. After that, MTE tag