linux-kernel - Re: [PATCH v7 00/11] kconfig: Add support for conflict resolution

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Z6oeplCypN825pyR@bombadil.infradead.org>
Date: Mon, 10 Feb 2025 07:43:34 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Ole Schuerks <ole0811sch@...il.com>, linux-kbuild@...r.kernel.org,
	jude.gyimah@....de, thorsten.berger@....de, deltaone@...ian.org,
	jan.sollmann@....de, linux-kernel@...r.kernel.org,
	nathan@...nel.org, nicolas@...sle.eu
Subject: Re: [PATCH v7 00/11] kconfig: Add support for conflict resolution

On Mon, Feb 10, 2025 at 02:00:52PM +0900, Masahiro Yamada wrote:
> Thanks for this, but I have no plans to merge the SAT solver.
> 
> The reason is that my future plan is to move toolchain selection
> to the Kconfig stage instead of specifying it statically from the command line.

That makes sense.

> This approach was suggested by Linus [1], and to achieve that,
> the shell evaluation must be dynamically re-evaluated [2].

Sure.

> The SAT solver would likely conflict with this plan. At least due to the
> significant amount of additional code, which would be an obstacle.

I can't see how the toolchain selection, if set on Kconfig can't be
leveraged later to enable / disable the SAT solver, however I can
see the amount of code shuffling incurred to be an extra hurdle to
address and a preference to leave that for later.

In other words, I susepct it is still possible to evaluate to
add support for the SAT solver post toolchain kconfig integration.

Thoughts?

 Luis