From: patchwork-bot+netdevbpf@kernel.org
To: Xu Kuohai <xukuohai@huawei.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, daniel@iogearbox.net,
ast@kernel.org, zlim.lnx@gmail.com, catalin.marinas@arm.com,
will@kernel.org, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org
Subject: Re: [PATCH bpf-next v2] bpf, arm64: Sign return address for jited code
Date: Tue, 05 Apr 2022 22:10:13 +0000 [thread overview]
Message-ID: <164919661303.14188.16221204846341071276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220402073942.3782529-1-xukuohai@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sat, 2 Apr 2022 03:39:42 -0400 you wrote:
> Sign return address for jited code when the kernel is built with pointer
> authentication enabled.
>
> 1. Sign LR with paciasp instruction before LR is pushed to stack. Since
> paciasp acts like landing pads for function entry, no need to insert
> bti instruction before paciasp.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf, arm64: Sign return address for jited code
https://git.kernel.org/bpf/bpf-next/c/042152c27c3b
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-04-06 5:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 7:39 [PATCH bpf-next v2] bpf, arm64: Sign return address for jited code Xu Kuohai
2022-04-05 22:10 ` 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=164919661303.14188.16221204846341071276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=will@kernel.org \
--cc=xukuohai@huawei.com \
--cc=yhs@fb.com \
--cc=zlim.lnx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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