netdev - Re: [PATCH] [net] nvmem: disallow modular 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: <CAK8P3a0wWw7Ue4SDcEMvbaNLQJnz0zeH31WZ0oXVNb0fWYP5LQ@mail.gmail.com>
Date:   Wed, 4 Apr 2018 15:38:22 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Mike Looijmans <mike.looijmans@...ic.nl>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        Andrew Lunn <andrew@...n.ch>,
        "David S . Miller" <davem@...emloft.net>,
        Networking <netdev@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Oleksij Rempel <o.rempel@...gutronix.de>,
        Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [net] nvmem: disallow modular CONFIG_NVMEM

On Wed, Apr 4, 2018 at 3:32 PM, Mike Looijmans <mike.looijmans@...ic.nl> wrote:

>
> Which may still be very confusing, since it means that CONFIG_MACB=y with
> CONFIG_NVMEM=m will fail, but setting both to "y" or both to "m" will work.
> So that would introduce more build failures again, right?

Right, it would require having a

      depends on NVMEM || !NVMEM

line in Kconfig for each such driver, or a

      depends on NVMEM != m

for drivers that cannot be modules themselves.

      Arnd