[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165186923712.2156651.13479757595045860724.b4-ty@chromium.org>
Date: Fri, 6 May 2022 13:33:59 -0700
From: Kees Cook <keescook@...omium.org>
To: linux-kernel@...r.kernel.org, mark.rutland@....com,
linux-arm-kernel@...ts.infradead.org
Cc: Kees Cook <keescook@...omium.org>, alex.popov@...ux.com
Subject: Re: [PATCH] lkdtm/stackleak: fix CONFIG_GCC_PLUGIN_STACKLEAK=n
On Fri, 6 May 2022 13:11:45 +0100, Mark Rutland wrote:
> Recent rework broke building LKDTM when CONFIG_GCC_PLUGIN_STACKLEAK=n.
> This patch fixes that breakage.
>
> Prior to recent stackleak rework, the LKDTM STACKLEAK_ERASING code could
> be built when the kernel was not built with stackleak support, and would
> run a test that would almost certainly fail (or pass by sheer cosmic
> coincidence), e.g.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] lkdtm/stackleak: fix CONFIG_GCC_PLUGIN_STACKLEAK=n
https://git.kernel.org/kees/c/932c12ae7963
--
Kees Cook
Powered by blists - more mailing lists