From: patchwork-bot+netdevbpf@kernel.org
To: Peter Zijlstra <peterz@infradead.org>
Cc: alexei.starovoitov@gmail.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, davem@davemloft.net,
dsahern@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, arnd@arndb.de,
samitolvanen@google.com, keescook@chromium.org,
nathan@kernel.org, ndesaulniers@google.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-arch@vger.kernel.org, llvm@lists.linux.dev,
jpoimboe@kernel.org, joao@overdrivepizza.com,
mark.rutland@arm.com
Subject: Re: [PATCH v3 0/7] x86/cfi,bpf: Fix CFI vs eBPF
Date: Sat, 16 Dec 2023 00:50:25 +0000 [thread overview]
Message-ID: <170268782592.26334.17481945540978625909.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231215091216.135791411@infradead.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 15 Dec 2023 10:12:16 +0100 you wrote:
> Hi!
>
> What started with the simple observation that bpf_dispatcher_*_func() was
> broken for calling CFI functions with a __nocfi calling context for FineIBT
> ended up with a complete BPF wide CFI fixup.
>
> With these changes on the BPF selftest suite passes without crashing -- there's
> still a few failures, but Alexei has graciously offered to look into those.
>
> [...]
Here is the summary with links:
- [v3,1/7] cfi: Flip headers
https://git.kernel.org/bpf/bpf-next/c/4382159696c9
- [v3,2/7] x86/cfi,bpf: Fix BPF JIT call
https://git.kernel.org/bpf/bpf-next/c/4f9087f16651
- [v3,3/7] x86/cfi,bpf: Fix bpf_callback_t CFI
https://git.kernel.org/bpf/bpf-next/c/e72d88d18df4
- [v3,4/7] x86/cfi,bpf: Fix bpf_struct_ops CFI
https://git.kernel.org/bpf/bpf-next/c/2cd3e3772e41
- [v3,5/7] cfi: Add CFI_NOSEAL()
https://git.kernel.org/bpf/bpf-next/c/e9d13b9d2f99
- [v3,6/7] bpf: Fix dtor CFI
https://git.kernel.org/bpf/bpf-next/c/e4c00339891c
- [v3,7/7] x86/cfi,bpf: Fix bpf_exception_cb() signature
https://git.kernel.org/bpf/bpf-next/c/852486b35f34
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-16 0:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 9:12 [PATCH v3 0/7] x86/cfi,bpf: Fix CFI vs eBPF Peter Zijlstra
2023-12-15 9:12 ` [PATCH v3 1/7] cfi: Flip headers Peter Zijlstra
2023-12-15 9:12 ` [PATCH v3 2/7] x86/cfi,bpf: Fix BPF JIT call Peter Zijlstra
2023-12-15 9:12 ` [PATCH v3 3/7] x86/cfi,bpf: Fix bpf_callback_t CFI Peter Zijlstra
2023-12-15 9:12 ` [PATCH v3 4/7] x86/cfi,bpf: Fix bpf_struct_ops CFI Peter Zijlstra
2023-12-15 9:12 ` [PATCH v3 5/7] cfi: Add CFI_NOSEAL() Peter Zijlstra
2023-12-15 9:12 ` [PATCH v3 6/7] bpf: Fix dtor CFI Peter Zijlstra
2023-12-15 9:12 ` [PATCH v3 7/7] x86/cfi,bpf: Fix bpf_exception_cb() signature Peter Zijlstra
2023-12-16 0:50 ` patchwork-bot+netdevbpf [this message]
2023-12-16 0:53 ` [PATCH v3 0/7] x86/cfi,bpf: Fix CFI vs eBPF Alexei Starovoitov
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=170268782592.26334.17481945540978625909.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=haoluo@google.com \
--cc=hpa@zytor.com \
--cc=joao@overdrivepizza.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yonghong.song@linux.dev \
/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