Searched refs:kunit_test (Results 1 – 7 of 7) sorted by relevance
| /Linux-v6.1/lib/kunit/ |
| D | test.c | 33 if (!current->kunit_test) in __kunit_fail_current_test()
36 kunit_set_failure(current->kunit_test); in __kunit_fail_current_test()
43 buffer = kunit_kmalloc(current->kunit_test, len, GFP_KERNEL); in __kunit_fail_current_test()
51 kunit_err(current->kunit_test, "%s:%d: %s", file, line, buffer); in __kunit_fail_current_test()
52 kunit_kfree(current->kunit_test, buffer); in __kunit_fail_current_test()
385 current->kunit_test = test; in kunit_try_run_case()
765 current->kunit_test = NULL; in kunit_cleanup()
|
| /Linux-v6.1/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 | usage.rst | 622 This test-only code can be made more useful by accessing the current ``kunit_test``
631 ``kunit_test`` field in ``task_struct``, we can access it via
632 ``current->kunit_test``.
647 struct kunit *test = current->kunit_test;
|
| D | running_tips.rst | 210 As of 5.13, the only difference is that ``current->kunit_test`` will
|
| /Linux-v6.1/mm/kasan/ |
| D | report.c | 124 test = current->kunit_test; in update_kunit_status()
|
| /Linux-v6.1/include/linux/ |
| D | sched.h | 1378 struct kunit *kunit_test; member
|
| /Linux-v6.1/mm/ |
| D | slub.c | 606 if (likely(!current->kunit_test)) in slab_add_kunit_errors()
609 resource = kunit_find_named_resource(current->kunit_test, "slab_errors"); in slab_add_kunit_errors()
|
