Lines Matching refs:report

101 When it is enabled, KASAN panics the kernel after printing a bug report.
103 By default, KASAN prints a bug report only for the first invalid memory access.
104 With ``kasan_multi_shot``, KASAN prints a report on every invalid access. This
110 - ``kasan.fault=report``, ``=panic``, or ``=panic_on_write`` controls whether
111   to only print a KASAN report, panic the kernel, or panic the kernel on
112   invalid writes only (default: ``report``). The panic happens even if
166 A typical KASAN report looks like this::
239 The report header summarizes what kind of bug happened and what kind of access
243 bug report). Next comes a description of the accessed slab object and the
246 In the end, the report shows the memory state around the accessed address.
249 memory state section of the report shows the state of one of the memory
262 In the report above, the arrow points to the shadow byte ``03``, which means
265 For tag-based KASAN modes, this last report section shows the memory tags around
334 report.
338 memory checks inline). With outline instrumentation mode, a bug report is
362 tag mismatch, a fault is generated, and a report is printed.
514 When a test fails due to a missing KASAN report::