Lines Matching full:reports

4  * For each test case checks the presence (or absence) of generated reports.
5  * Relies on 'console' tracepoint to capture reports as they appear in the
184 	kunit_info(test, "initialized kmalloc test (no reports)\n");  in test_init_kmalloc()
197 	kunit_info(test, "initialized kzalloc test (no reports)\n");  in test_init_kzalloc()
220 	kunit_info(test, "initialized stack variable (no reports)\n");  in test_init_stack_var()
295  * Test case: ensure kmsan_check_memory() reports an error when checking
323 	kunit_info(test, "pages initialized via vmap (no reports)\n");  in test_init_kmsan_vmap_vunmap()
353 	kunit_info(test, "vmalloc buffer can be initialized (no reports)\n");  in test_init_vmalloc()
438 		"memcpy()ing aligned initialized src to aligned dst (no reports)\n");  in test_init_memcpy()
467  * aligned 4-byte values. This test case checks that KMSAN correctly reports an
509  * the origin is nonzero (i.e. KMSAN reports an error).
519 		"unaligned 4-byte initialized value gets a nonzero origin after memcpy() - (2 UMR reports)\n");  in test_memcpy_initialized_gap()
603 	kunit_info(test, "testing stackdepot roundtrip (no reports)\n");  in test_stackdepot_roundtrip()
628 		"unpoisoning via the instrumentation vs. kmsan_unpoison_memory() (2 UMR reports)\n");  in test_unpoison_memory()