Bug 198441
Summary: | KASAN: need tests that check reports | ||
---|---|---|---|
Product: | Memory Management | Reporter: | Dmitry Vyukov (dvyukov) |
Component: | Sanitizers | Assignee: | Dmitry Vyukov (dvyukov) |
Status: | NEW --- | ||
Severity: | enhancement | CC: | andreyknvl, kasan-dev |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | ALL | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Dmitry Vyukov
2018-01-10 14:34:29 UTC
*** Bug 202773 has been marked as a duplicate of this bug. *** "KUnit-KASAN Integration" patchset [1] (not merged yet) addresses checking whether KASAN is expected to detect a bug for each test. [1] https://lore.kernel.org/patchwork/project/lkml/list/?series=447332 Checking the contents of reports can be implemented in the same way as in KFENCE, see probe_console(). Arguably, this bug is duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=212203. KASAN tests have been switched to using console tracepoints in [1]. The next step is to implement the tests' contents checks. Note: for use-after-realloc tests (including kmalloc_uaf3), the checks must ensure that the alloc/free stack traces point to the right alloc/free. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7ce0ea19d50e4e97a8da69f616ffa8afbb532a93 |