Searched refs:kunit_test (Results 1 – 7 of 7) sorted by relevance
| /linux-6.3-rc2/lib/kunit/ |
| A D | test.c | 33 if (!current->kunit_test) in __kunit_fail_current_test_impl()
36 kunit_set_failure(current->kunit_test); in __kunit_fail_current_test_impl()
43 buffer = kunit_kmalloc(current->kunit_test, len, GFP_KERNEL); in __kunit_fail_current_test_impl()
51 kunit_err(current->kunit_test, "%s:%d: %s", file, line, buffer); in __kunit_fail_current_test_impl()
52 kunit_kfree(current->kunit_test, buffer); in __kunit_fail_current_test_impl()
384 current->kunit_test = test; in kunit_try_run_case()
770 current->kunit_test = NULL; in kunit_cleanup()
|
| /linux-6.3-rc2/include/kunit/ |
| A D | test-bug.h | 44 return current->kunit_test; in kunit_get_current_test()
|
| /linux-6.3-rc2/mm/kasan/ |
| A D | report.c | 156 test = current->kunit_test; in fail_non_kasan_kunit_test()
|
| /linux-6.3-rc2/Documentation/dev-tools/kunit/ |
| A D | running_tips.rst | 210 As of 5.13, the only difference is that ``current->kunit_test`` will
|
| A D | usage.rst | 638 This test-only code can be made more useful by accessing the current ``kunit_test``
647 We can do this via the ``kunit_test`` field in ``task_struct``, which we can
|
| /linux-6.3-rc2/include/linux/ |
| A D | sched.h | 1378 struct kunit *kunit_test; member
|
| /linux-6.3-rc2/mm/ |
| A D | slub.c | 625 resource = kunit_find_named_resource(current->kunit_test, "slab_errors"); in slab_add_kunit_errors()
|
Completed in 28 milliseconds