Searched refs:kunit_test (Results 1 – 8 of 8) sorted by relevance
/linux/rust/kernel/ |
H A D | kunit.rs | 64 let kunit_test = unsafe { $crate::bindings::kunit_get_current_test() }; localVariable 65 if kunit_test.is_null() { 130 kunit_test, 143 $crate::bindings::__kunit_abort(kunit_test);
|
/linux/lib/kunit/ |
H A D | kunit-test.c | 508 kunit_log(KERN_INFO, current->kunit_test, "action_order_1"); in action_order_1() 515 kunit_log(KERN_INFO, current->kunit_test, "action_order_2"); in action_order_2() 708 KUNIT_EXPECT_PTR_EQ(test, test, current->kunit_test); in kunit_current_test() 720 current->kunit_test = &fake; in kunit_current_fail_test() 727 current->kunit_test = test; in kunit_current_fail_test()
|
/linux/include/kunit/ |
H A D | test-bug.h | 46 return current->kunit_test; in kunit_get_current_test()
|
/linux/mm/kasan/ |
H A D | report.c | 193 test = current->kunit_test; in fail_non_kasan_kunit_test()
|
/linux/Documentation/dev-tools/kunit/ |
H A D | usage.rst | 718 This test-only code can be made more useful by accessing the current ``kunit_test`` 727 We can do this via the ``kunit_test`` field in ``task_struct``, which we can
|
H A D | running_tips.rst | 221 As of 5.13, the only difference is that ``current->kunit_test`` will
|
/linux/include/linux/ |
H A D | sched.h | 1457 struct kunit *kunit_test; member
|
/linux/mm/ |
H A D | slub.c | 811 resource = kunit_find_named_resource(current->kunit_test, "slab_errors"); in slab_add_kunit_errors() 827 resource = kunit_find_named_resource(current->kunit_test, "slab_errors"); in slab_in_kunit_test()
|