[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166753802702.27738.11594925007780721329.git-patchwork-notify@kernel.org>
Date: Fri, 04 Nov 2022 05:00:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Nathan Chancellor <nathan@...nel.org>
Cc: t.sailer@...mni.ethz.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, linux-hams@...r.kernel.org,
netdev@...r.kernel.org, ndesaulniers@...gle.com, trix@...hat.com,
keescook@...omium.org, samitolvanen@...gle.com,
llvm@...ts.linux.dev, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH] hamradio: baycom_epp: Fix return type of baycom_send_packet()
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 2 Nov 2022 09:06:10 -0700 you 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:
>
> [...]
Here is the summary with links:
- hamradio: baycom_epp: Fix return type of baycom_send_packet()
https://git.kernel.org/netdev/net-next/c/c5733e5b15d9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists