linux-kernel - kconfig usage in automatic kernel test

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 6 Jul 2018 16:49:25 +0800
From:   Cao jin <caoj.fnst@...fujitsu.com>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
CC:     Michal Marek <michal.lkml@...kovi.net>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: kconfig usage in automatic kernel test

Masahiro-san,

  I am writing some utility for internal kdump test with latest kernel,
my purpose is to test the new introduced kernel feature. For automatical
test, I see several config target could help, like olddefconfig, all*config.

But for my purpose, I don't find a good way. For example, olddefconfig
will let the now config item has default value, while some feature may
default to "N"; allyesconfig will slow the compilation notably.
But "all*config" has KCONFIG_ALLCONFIG help to customizing some config
item, that is a good utility, but seems it can't be used in olddefconfig.

All these things let me have 2 questions:

1. What would you suggest for my purpose?

2. allyesconfig, allmodconfig, randconfig seems useful for test kbuild,
but what's the purpose of allnoconfig, alldefconfig? In others words,
when people would need allnoconfig, alldefconfig?
-- 
Sincerely,
Cao jin