linux-kernel - s390 depending on cc-options makes it difficult to configure

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

Date:   Mon, 9 Dec 2019 11:41:55 -0500
From:   Jeremy Cline <jcline@...hat.com>
To:     Heiko Carstens <heiko.carstens@...ibm.com>,
        Vasily Gorbik <gor@...ux.ibm.com>
Cc:     linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: s390 depending on cc-options makes it difficult to configure

Hi folks,

Commit 5474080a3a0a ("s390/Kconfig: make use of 'depends on cc-option'")
makes it difficult to produce an s390 configuration for Fedora and Red
Hat kernels.

The issue is I have the following configurations:

CONFIG_MARCH_Z13=y
CONFIG_TUNE_Z14=y
# CONFIG_TUNE_DEFAULT is not set

When the configuration is prepared on a non-s390x host without a
compiler with -march=z* it changes CONFIG_TUNE_DEFAULT to y which, as
far as I can tell, leads to a kernel tuned for z13 instead of z14.
Fedora and Red Hat build processes produce complete configurations from
snippets on any available host in the build infrastructure which very
frequently is *not* s390.

I did a quick search and couldn't find any other examples of Kconfigs
depending on march or mtune compiler flags and it seems like it'd
generally problematic for people preparing configurations.

Regards,
Jeremy