Thread (152 messages) 152 messages, 21 authors, 2021-08-13

Re: [PATCH 33/64] lib: Introduce CONFIG_TEST_MEMCPY

From: Randy Dunlap <hidden>
Date: 2021-07-27 23:33:38
Also in: dri-devel, linux-hardening, linux-kbuild, linux-staging, linux-wireless, lkml, netdev

On 7/27/21 4:31 PM, Bart Van Assche wrote:
On 7/27/21 1:58 PM, Kees Cook wrote:
quoted
+static int __init test_memcpy_init(void)
+{
+    int err = 0;
+
+    err |= test_memcpy();
+    err |= test_memmove();
+    err |= test_memset();
+
+    if (err) {
+        pr_warn("FAIL!\n");
+        err = -EINVAL;
+    } else {
+        pr_info("all tests passed\n");
+    }
+
+    return err;
+}
+
+static void __exit test_memcpy_exit(void)
+{ }
+
+module_init(test_memcpy_init);
+module_exit(test_memcpy_exit);
+MODULE_LICENSE("GPL");
Has it been considered to implement this test using the Kunit framework?
and do we want everything converted to use the Kunit test framework?

My answer is No, we don't, but I could easily be in the minority.

-- 
~Randy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help