linux-kernel - Re: [PATCH] Make "Memory Debugging" a menuconfig to ease disabling it all

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: <CAEwRq=pU1PzRrXRwqnardTofFafb2OGYsS36ZxWdXcfHD6iWZw@mail.gmail.com>
Date:   Sat, 9 Dec 2017 13:40:17 +0100
From:   Vincent Legoll <vincent.legoll@...il.com>
To:     Andrew Morton <akpm@...ux-foundation.org>,
        Ingo Molnar <mingo@...nel.org>,
        Byungchul Park <byungchul.park@....com>,
        Peter Zijlstra <peterz@...radead.org>,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Randy Dunlap <rdunlap@...radead.org>,
        "Luis R. Rodriguez" <mcgrof@...nel.org>,
        Nicholas Piggin <npiggin@...il.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Linux Kernel ML <linux-kernel@...r.kernel.org>
Cc:     Vincent Legoll <vincent.legoll@...il.com>
Subject: Re: [PATCH] Make "Memory Debugging" a menuconfig to ease disabling it all

This patch introduces some Kconfig warnings:

warning: (X86) selects HAVE_DEBUG_KMEMLEAK which has unmet direct
dependencies (DEBUG_MEMORY)
warning: (X86) selects HAVE_ARCH_KASAN which has unmet direct
dependencies (DEBUG_MEMORY)
warning: (X86) selects ARCH_HAS_DEBUG_VIRTUAL which has unmet direct
dependencies (DEBUG_MEMORY)
warning: (X86) selects HAVE_DEBUG_STACKOVERFLOW which has unmet direct
dependencies (DEBUG_MEMORY)

What would be the best way to fix that ?

excluding those config options from the "if DEBUG_MEMORY" code
block seems to alleviate the warnings, but is that OK to do ?

Would moving them out of the if/endif block be acceptable ?

Thanks

-- 
Vincent Legoll