From: patchwork-bot+netdevbpf@kernel.org
To: Uros Bizjak <ubizjak@gmail.com>
Cc: x86@kernel.org, bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net
Subject: Re: [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff
Date: Tue, 02 Apr 2024 04:10:28 +0000 [thread overview]
Message-ID: <171203102833.24910.7566029980709800852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240401185821.224068-1-ubizjak@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 1 Apr 2024 20:55:28 +0200 you wrote:
> From: Joan Bruguera Micó <joanbrugueram@gmail.com>
>
> Fixes two issues that cause kernels panic when using the BPF JIT with
> the call depth tracking / stuffing mitigation for Skylake processors
> (`retbleed=stuff`). Both issues can be triggered by running simple
> BPF programs (e.g. running the test suite should trigger both).
>
> [...]
Here is the summary with links:
- [RESEND,bpf,v2,1/2] x86/bpf: Fix IP after emitting call depth accounting
https://git.kernel.org/bpf/bpf/c/9d98aa088386
- [RESEND,bpf,v2,2/2] x86/bpf: Fix IP for relocating call depth accounting
https://git.kernel.org/bpf/bpf/c/6a537453000a
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:[~2024-04-02 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 18:55 [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff Uros Bizjak
2024-04-01 18:55 ` [PATCH RESEND bpf v2 1/2] x86/bpf: Fix IP after emitting call depth accounting Uros Bizjak
2024-04-01 18:55 ` [PATCH RESEND bpf v2 2/2] x86/bpf: Fix IP for relocating " Uros Bizjak
2024-04-02 4:10 ` patchwork-bot+netdevbpf [this message]
2024-04-03 7:26 ` [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff Ingo Molnar
2024-04-03 7:43 ` Uros Bizjak
2024-04-03 8:01 ` Ingo Molnar
2024-04-03 9:04 ` Daniel Borkmann
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=171203102833.24910.7566029980709800852.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.org \
/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