Searched refs:kunit_test (Results 1 – 6 of 6) sorted by relevance
| /Linux-v5.15/mm/kasan/ |
| D | report.c | 373 if (current->kunit_test) in kasan_report_invalid_free()
374 kasan_update_kunit_status(current->kunit_test); in kasan_report_invalid_free()
393 if (current->kunit_test) in kasan_report_async()
394 kasan_update_kunit_status(current->kunit_test); in kasan_report_async()
415 if (current->kunit_test) in __kasan_report()
416 kasan_update_kunit_status(current->kunit_test); in __kasan_report()
|
| /Linux-v5.15/lib/kunit/ |
| D | test.c | 31 if (!current->kunit_test) in __kunit_fail_current_test()
34 kunit_set_failure(current->kunit_test); in __kunit_fail_current_test()
41 buffer = kunit_kmalloc(current->kunit_test, len, GFP_KERNEL); in __kunit_fail_current_test()
49 kunit_err(current->kunit_test, "%s:%d: %s", file, line, buffer); in __kunit_fail_current_test()
50 kunit_kfree(current->kunit_test, buffer); in __kunit_fail_current_test()
367 current->kunit_test = test; in kunit_try_run_case()
790 current->kunit_test = NULL; in kunit_cleanup()
|
| /Linux-v5.15/Documentation/dev-tools/kunit/ |
| D | tips.rst | 90 There is a ``kunit_test`` field in ``task_struct``, so you can access it via
91 ``current->kunit_test``.
106 struct kunit *test = current->kunit_test;
|
| D | running_tips.rst | 203 As of 5.13, the only difference is that ``current->kunit_test`` will
|
| /Linux-v5.15/include/linux/ |
| D | sched.h | 1349 struct kunit *kunit_test; member
|
| /Linux-v5.15/mm/ |
| D | slub.c | 554 if (likely(!current->kunit_test)) in slab_add_kunit_errors()
557 resource = kunit_find_named_resource(current->kunit_test, "slab_errors"); in slab_add_kunit_errors()
|
