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  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]
Date:   Wed, 8 Apr 2020 16:38:29 -0400 (EDT)
From:   Nicolas Pitre <>
To:     Arnd Bergmann <>
        Masahiro Yamada <>,
        Andrzej Hajda <>,
        Neil Armstrong <>,
        Laurent Pinchart <>,
        Jonas Karlman <>,
        Jernej Skrabec <>,
        David Airlie <>,
        Daniel Vetter <>,
        Kieran Bingham <>,
        "David S. Miller" <>,
        Saeed Mahameed <>,
        Leon Romanovsky <>,,,,
Subject: Re: [RFC 0/6] Regressions for "imply" behavior change

On Wed, 8 Apr 2020, Arnd Bergmann wrote:

> Hi everyone,
> I've just restarted doing randconfig builds on top of mainline Linux and
> found a couple of regressions with missing dependency from the recent
> change in the "imply" keyword in Kconfig, presumably these two patches:
> 3a9dd3ecb207 kconfig: make 'imply' obey the direct dependency
> def2fbffe62c kconfig: allow symbols implied by y to become m
> I have created workarounds for the Kconfig files, which now stop using
> imply and do something else in each case. I don't know whether there was
> a bug in the kconfig changes that has led to allowing configurations that
> were not meant to be legal even with the new semantics, or if the Kconfig
> files have simply become incorrect now and the tool works as expected.

In most cases it is the code that has to be fixed. It typically does:


Where it should rather do:


A couple of such patches have been produced and queued in their 
respective trees already.


Powered by blists - more mailing lists