Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Neil Armstrong <neil.armstrong@linaro.org>
To:     Nathan Chancellor <nathan@kernel.org>
Cc:     patches@lists.linux.dev, dri-devel@lists.freedesktop.org,
        Kees Cook <keescook@chromium.org>, llvm@lists.linux.dev,
        linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
        Tom Rix <trix@redhat.com>,
        Sami Tolvanen <samitolvanen@google.com>,
        Nick Desaulniers <ndesaulniers@google.com>
In-Reply-To: <20221102155242.1927166-1-nathan@kernel.org>
References: <20221102155242.1927166-1-nathan@kernel.org>
Subject: Re: [PATCH] drm/meson: Fix return type of meson_encoder_cvbs_mode_valid()
Message-Id: <166746490033.1047451.8509801800691914580.b4-ty@linaro.org>
Date:   Thu, 03 Nov 2022 09:41:40 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi,

On Wed, 2 Nov 2022 08:52:42 -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:
> 
> [...]

Thanks, Applied to https://anongit.freedesktop.org/git/drm/drm-misc.git (drm-misc-next)

[1/1] drm/meson: Fix return type of meson_encoder_cvbs_mode_valid()
      https://cgit.freedesktop.org/drm/drm-misc/commit/?id=6c4e4d35203301906afb53c6d1e1302d4c793c05

-- 
Neil