Searched refs:kunit_test (Results 1 – 6 of 6) sorted by relevance
| /linux/mm/kasan/ |
| A D | report.c | 364 if (current->kunit_test) in kasan_report_invalid_free()
365 kasan_update_kunit_status(current->kunit_test); in kasan_report_invalid_free()
384 if (current->kunit_test) in kasan_report_async()
385 kasan_update_kunit_status(current->kunit_test); in kasan_report_async()
406 if (current->kunit_test) in __kasan_report()
407 kasan_update_kunit_status(current->kunit_test); in __kasan_report()
|
| /linux/lib/kunit/ |
| A 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()
792 current->kunit_test = NULL; in kunit_cleanup()
|
| /linux/Documentation/dev-tools/kunit/ |
| A 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;
|
| A D | running_tips.rst | 210 As of 5.13, the only difference is that ``current->kunit_test`` will
|
| /linux/include/linux/ |
| A D | sched.h | 1345 struct kunit *kunit_test; member
|
| /linux/mm/ |
| A D | slub.c | 577 if (likely(!current->kunit_test)) in slab_add_kunit_errors()
580 resource = kunit_find_named_resource(current->kunit_test, "slab_errors"); in slab_add_kunit_errors()
|
Completed in 31 milliseconds