[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <166067790682.7084.237943534143309650.b4-ty@chromium.org>
Date: Tue, 16 Aug 2022 12:25:08 -0700
From: Kees Cook <keescook@...omium.org>
To: linuxppc-dev@...ts.ozlabs.org, linux-hardening@...r.kernel.org,
ajd@...ux.ibm.com
Cc: Kees Cook <keescook@...omium.org>, yury.norov@...il.com,
erhard_f@...lbox.org
Subject: Re: [PATCH] gcc-plugins: Undefine LATENT_ENTROPY_PLUGIN when plugin disabled for a file
On Tue, 16 Aug 2022 15:17:20 +1000, Andrew Donnellan wrote:
> Commit 36d4b36b6959 ("lib/nodemask: inline next_node_in() and
> node_random()") refactored some code by moving node_random() from
> lib/nodemask.c to include/linux/nodemask.h, thus requiring nodemask.h to
> include random.h, which conditionally defines add_latent_entropy()
> depending on whether the macro LATENT_ENTROPY_PLUGIN is defined.
>
> This broke the build on powerpc, where nodemask.h is indirectly included
> in arch/powerpc/kernel/prom_init.c, part of the early boot machinery that
> is excluded from the latent entropy plugin using
> DISABLE_LATENT_ENTROPY_PLUGIN. It turns out that while we add a gcc flag
> to disable the actual plugin, we don't undefine LATENT_ENTROPY_PLUGIN.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] gcc-plugins: Undefine LATENT_ENTROPY_PLUGIN when plugin disabled for a file
https://git.kernel.org/kees/c/2d08c71d2c79
--
Kees Cook
Powered by blists - more mailing lists