linux-kernel - Re: linux-next: build warning in Linus' tree

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: <CA+55aFwDL2_Ecuei4tYLH34RDmOba_COfr5JajasvYXA++yUgA@mail.gmail.com>
Date:   Thu, 27 Oct 2016 16:01:22 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Andrey Ryabinin <aryabinin@...tuozzo.com>,
        Alexander Potapenko <glider@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>
Cc:     linux-next <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warning in Linus' tree

On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
> does seem to disable a lot of build-time testing.

Actually, we should probably just make the MEMORY_HOTPLUG dependency be

        depends on COMPILE_TEST || !KASAN

since the memory-hotplug code should still *build* with KASAN, it just
doesn't work. That's exactly what the COMPILE_TEST config option is
there for - to get build coverage even for things that aren't
necessarily sane to run.

I'll do that, to get my build coverage up. I really expected my
allmodconfig builds to verify that I had removed the per-zone
waitqueue code completely, and I'm happy that the breakage was
apparently limited to that unused variable..

In the meantime, thanks for noticing and letting me know.

            Linus