linux-kernel - Re: The UAPI references Kconfig's 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] [day] [month] [year] [list]

Message-ID: <CAK8P3a3g4Fb_027dkTMXeLLGQ+OevCc26-x7sx6FrK1BT4Nxfw@mail.gmail.com>
Date:   Wed, 15 May 2019 23:09:49 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Michael Witten <mfwitten@...il.com>
Cc:     Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Michal Marek <michal.lkml@...kovi.net>,
        David Woodhouse <dwmw2@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: The UAPI references Kconfig's CONFIG_* macros (variables)

On Sat, May 11, 2019 at 6:29 AM Michael Witten <mfwitten@...il.com> wrote:

>
> What is the correct way to think about this?
>
>   * Should the UAPI make no reference to build-time configurations?

Right, with the exception of uses inside of #ifdef __KERNEL__.

>   * Should the UAPI headers include sanity checks on behalf of the user?
>   * Should there be a `/proc/config.h.gz' facility?

This would not work, since applications don't always run on the systems
they are compiled on, in particular when cross-compiling to another
architecture.

      Arnd