linux-kernel - Re: [PATCH 3/3] Kconfig: add a default allrandom.config

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK7LNAQVSVtXzWXjLRAQXynSvHHbiF1xYLhjLBwPfFOpnX_NRA@mail.gmail.com>
Date:   Tue, 20 Feb 2018 18:16:17 +0900
From:   Masahiro Yamada <yamada.masahiro@...ionext.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        "Yann E . MORIN" <yann.morin.1998@...e.fr>,
        Michal Marek <mmarek@...e.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] Kconfig: add a default allrandom.config

2018-02-17 6:41 GMT+09:00 Arnd Bergmann <arnd@...db.de>:
> Building randconfig kernels frequently leads to build errors from
> drivers that have additional build dependencies, or that we don't
> want to build for compile-testing for some other reason.

Can you fix the former case?

The latter seems OK.


> We already have a couple of compile-time options that can deal with this
> problem, but the complete set is not documented well.  We also have a
> method to override some options during 'make randconfig' and a couple
> of other make targets. However, we don't yet combine those two.


>From this statement,

kernel/configs/compile_test.config

would make more sense?




> This adds a new allrandom.config file to turn on CONFIG_COMPILE_TEST,
> CONFIG_STANDALONE and CONFIG_PREVENT_FIRMWARE_BUILD for all randconfig
> builds. This in turn disables some other options that we already try
> to avoid in 'allmodconfig' builds and that make no sense in a general
> randconfig build.
>
> Building with 'make randconfig KCONFIG_ALLCONFIG=1' should now always


Can you type 'make randconfig compile_test.config', instead?

(Or 'make allmodconfig compile_test.config' for full-build test)


The merge_config has a little bit different logic
from KCONFIG_ALLCONFIG=1, but I guess it leads to the almost same result.



> succeed without warnings on x86 and arm64, aside from recent regressions.
> Other architectures probably need additional bugfixes.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
>  kernel/configs/allrandom.config | 6 ++++++
>  1 file changed, 6 insertions(+)
>  create mode 100644 kernel/configs/allrandom.config
>
> diff --git a/kernel/configs/allrandom.config b/kernel/configs/allrandom.config
> new file mode 100644
> index 000000000000..67294ef2e3a2
> --- /dev/null
> +++ b/kernel/configs/allrandom.config
> @@ -0,0 +1,6 @@
> +# maximize search space, disable options not worth testing
> +CONFIG_COMPILE_TEST=y
> +
> +# reduce compile-time dependencies
> +CONFIG_STANDALONE=y
> +CONFIG_PREVENT_FIRMWARE_BUILD=y
> --
> 2.9.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Best Regards
Masahiro Yamada