[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <327831fb-47ab-4555-8f0b-19a8dbcaacd7@collabora.com>
Date: Mon, 15 Jul 2024 15:09:24 +0500
From: Muhammad Usama Anjum <usama.anjum@...labora.com>
To: Kees Cook <keescook@...omium.org>, Shuah Khan <shuah@...nel.org>,
davidgow@...gle.com
Cc: Muhammad Usama Anjum <usama.anjum@...labora.com>,
"open list : KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>, kunit-dev@...glegroups.com,
David Gow <davidgow@...gle.com>, "kernel@...labora.com"
<kernel@...labora.com>
Subject: Converting kselftest test modules to kunit
Hi Kees and All,
There are several tests in kselftest subsystem which load modules to tests
the internals of the kernel. Most of these test modules are just loaded by
the kselftest, their status isn't read and reported to the user logs. Hence
they don't provide benefit of executing those tests.
I've found patches from Kees where he has been converting such kselftests
to kunit tests [1]. The probable motivation is to move tests output of
kselftest subsystem which only triggers tests without correctly reporting
the results. On the other hand, kunit is there to test the kernel's
internal functions which can't be done by userspace.
Kselftest: Test user facing APIs from userspace
Kunit: Test kernel's internal functions from kernelspace
This brings me to conclusion that kselftest which are loading modules to
test kernelspace should be converted to kunit tests. I've noted several
such kselftests.
This is just my understanding. Please mention if I'm correct above or more
reasons to support kselftest test modules transformation into kunit test.
[1] https://lore.kernel.org/all/20221018082824.never.845-kees@kernel.org/
--
BR,
Muhammad Usama Anjum
Powered by blists - more mailing lists