[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dab5fc68-0ac5-306a-bd81-0165f3b741ec@huawei.com>
Date: Sat, 17 Sep 2022 20:40:49 +0800
From: "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>
To: Kees Cook <keescook@...omium.org>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Jiri Kosina <jikos@...nel.org>,
Miroslav Benes <mbenes@...e.cz>,
Petr Mladek <pmladek@...e.com>,
Joe Lawrence <joe.lawrence@...hat.com>,
<live-patching@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
"Masahiro Yamada" <masahiroy@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Jiri Olsa <jolsa@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Luis Chamberlain" <mcgrof@...nel.org>,
<linux-modules@...r.kernel.org>
Subject: Re: [PATCH v2 8/8] kallsyms: Add self-test facility
On 2022/9/17 16:07, Kees Cook wrote:
>
>
> On September 9, 2022 2:00:16 PM GMT+01:00, Zhen Lei <thunder.leizhen@...wei.com> wrote:
>> Add some test cases to test the function and performance of some kallsyms
>> interfaces, such as kallsyms_lookup_name. It also calculates the
>> compression rate of the kallsyms compression algorithm for the current
>> symbol set.
>>
>> Start self-test automatically after system startup.
if CONFIG_KALLSYMS_SELFTEST=y
>
> I wonder if this would be better implemented as a kunit test? Shouldn't be too hard to convert. Take a look at things like lib/overflow_kunit.c, etc.
Yes, I can try to define one for each type of symbol, such as: bss, data, weak, static.
In addition, we can use kallsyms_offsets[] to do a full test.
>
> -Kees
>
--
Regards,
Zhen Lei
Powered by blists - more mailing lists