Lines Matching full:reports

56 To include alloc and free stack traces of affected slab objects into reports,
60 Error reports
169 Generic KASAN also reports up to two auxiliary call stack traces. These stack
182 effectively disables ``panic_on_warn`` for KASAN reports.
204   only reports tag faults during these checks.
273 dedicated ``brk`` handler is used to print bug reports.
313 Hardware tag-based KASAN only reports the first found bug. After that, MTE tag
387 Normally, KASAN detects and reports such accesses, but in some cases (e.g.,
412 For software KASAN modes, to disable KASAN reports in a part of the kernel code
415 disables the reports for indirect accesses that happen through function calls.
436 kernel log for KASAN reports.
438 Each KUnit-compatible KASAN test prints one of multiple KASAN reports if an
482    readable way. This will not print the KASAN reports of the tests that passed.