linux-kernel - Re: [kconfig-sat] [ANN] init-kconfig - easy way to embrace Linux's kconfig

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: <20181004205319.GO5238@garbanzo.do-not-panic.com>
Date:   Thu, 4 Oct 2018 13:53:19 -0700
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Josh Triplett <josh@...htriplett.org>
Cc:     LKML <linux-kernel@...r.kernel.org>, linux-kbuild@...r.kernel.org,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        Sam Ravnborg <sam@...nborg.org>, Petr Vorel <pvorel@...e.cz>,
        Steven Rostedt <rostedt@...dmis.org>,
        Johannes Berg <johannes@...solutions.net>,
        Valentin Rothberg <valentinrothberg@...il.com>,
        Vegard Nossum <vegard.nossum@...cle.com>,
        Felix Fietkau <nbd@....name>, kconfig-sat@...glegroups.com
Subject: Re: [kconfig-sat] [ANN] init-kconfig - easy way to embrace Linux's
 kconfig

On Thu, Oct 04, 2018 at 01:41:18PM -0700, Josh Triplett wrote:
> I would *love* to see Kconfig in Linux evolved to be more easily reused.

This *can* happen. Let me itemize a few things off of my head I think
would need to be done as its at least fresh in my head now:

All we need from scripts/Kbuild.include is filechk and kecho (what I
have in my scripts/Kbuild.include). This could be moved to
scripts/Kbuild.basic, and so would make sync'ing easier.

The scripts/kconfig/Makefile would need a respective modifications to
make it work independently, see my scripts/kconfig/Makefile. Perhaps
the biggest pain was resolving the target for
scripts/kconfig/.mconf-cfg. If somehow we end up with a file which could
work for both environments we're set.

Other than this we'd need a simple script, say scripts/copy-kconfig.sh
which would copy over only those files I took from scripts/kconfig.

There's a few things to consider for a split copy / demo:

  * versioning *is not* part of kconfig
  * object building *is not* part of kconfig

But the problem I faced was that to demo kconfig I had to use *something*
for versioning and object building. The object building is simple, and
the versioning scheme was just copied from Linux.

What I ended up with the smallest demo I could come up with.

  Luis