From: patchwork-bot+netdevbpf@kernel•org
To: Nathan Chancellor <nathan@kernel•org>
Cc: t.sailer@alumni•ethz.ch, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
linux-hams@vger•kernel.org, netdev@vger•kernel.org,
ndesaulniers@google•com, trix@redhat•com, keescook@chromium•org,
samitolvanen@google•com, llvm@lists•linux.dev,
linux-kernel@vger•kernel.org, patches@lists•linux.dev
Subject: Re: [PATCH] hamradio: baycom_epp: Fix return type of baycom_send_packet()
Date: Fri, 04 Nov 2022 05:00:27 +0000 [thread overview]
Message-ID: <166753802702.27738.11594925007780721329.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221102160610.1186145-1-nathan@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•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
prev parent reply other threads:[~2022-11-04 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:06 [PATCH] hamradio: baycom_epp: Fix return type of baycom_send_packet() Nathan Chancellor
2022-11-02 19:08 ` Kees Cook
2022-11-04 5:00 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166753802702.27738.11594925007780721329.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-hams@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=nathan@kernel$(echo .)org \
--cc=ndesaulniers@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=patches@lists$(echo .)linux.dev \
--cc=samitolvanen@google$(echo .)com \
--cc=t.sailer@alumni$(echo .)ethz.ch \
--cc=trix@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox