[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166879319846.2080862.8296193513373990861.b4-ty@chromium.org>
Date: Fri, 18 Nov 2022 09:40:01 -0800
From: Kees Cook <keescook@...omium.org>
To: nathan@...nel.org, alison.wang@....com, stefan@...er.ch
Cc: Kees Cook <keescook@...omium.org>, llvm@...ts.linux.dev,
trix@...hat.com, samitolvanen@...gle.com, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
ndesaulniers@...gle.com
Subject: Re: [PATCH] drm/fsl-dcu: Fix return type of fsl_dcu_drm_connector_mode_valid()
On Wed, 2 Nov 2022 08:42:15 -0700, Nathan Chancellor wrote:
> With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
> indirect call targets are validated against the expected function
> pointer prototype to make sure the call target is valid to help mitigate
> ROP attacks. If they are not identical, there is a failure at run time,
> which manifests as either a kernel panic or thread getting killed. A
> proposed warning in clang aims to catch these at compile time, which
> reveals:
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] drm/fsl-dcu: Fix return type of fsl_dcu_drm_connector_mode_valid()
https://git.kernel.org/kees/c/96d845a67b7e
--
Kees Cook
Powered by blists - more mailing lists