diff options
| author |  Andrey Konovalov <andreyknvl@google.com>
| 2022-11-30 16:02:03 +0100 |
|---|---|---|
| committer |  Andrew Morton <akpm@linux-foundation.org>
| 2022-12-11 18:12:15 -0800 |
| commit | c8c7016f50c85688d71feea2dba1bd955d5f5358 (patch) | |
| tree | 95e1998b2fddcf5f4433ff00756d979696d902d1 /LICENSES | |
| parent | mm/hugetlb: change hugetlb allocation functions to return a folio (diff) | |
| download | linux-c8c7016f50c85688d71feea2dba1bd955d5f5358.tar.gz linux-c8c7016f50c85688d71feea2dba1bd955d5f5358.tar.bz2 linux-c8c7016f50c85688d71feea2dba1bd955d5f5358.zip | |
kasan: fail non-kasan KUnit tests on KASAN reports
After the recent changes done to KUnit-enabled KASAN tests, non-KASAN
KUnit tests stopped being failed when KASAN report is detected.
Recover that property by failing the currently running non-KASAN KUnit
test when KASAN detects and prints a report for a bad memory access.
Note that if the bad accesses happened in a kernel thread that doesn't
have a reference to the currently running KUnit-test available via
current->kunit_test, the test won't be failed. This is a limitation of
KUnit, which doesn't yet provide a thread-agnostic way to find the
reference to the currenly running test.
Link: https://lkml.kernel.org/r/7be29a8ea967cee6b7e48d3d5a242d1d0bd96851.1669820505.git.andreyknvl@google.com
Fixes: 49d9977ac909 ("kasan: check CONFIG_KASAN_KUNIT_TEST instead of CONFIG_KUNIT")
Fixes: 7ce0ea19d50e ("kasan: switch kunit tests to console tracepoints")
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: David Gow <davidgow@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Marco Elver <elver@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'LICENSES')
0 files changed, 0 insertions, 0 deletions