linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Luis Gerhorst <luis.gerhorst@fau.de>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, puranjay@kernel.org, xukuohai@huaweicloud.com,
	catalin.marinas@arm.com, will@kernel.org, hbathini@linux.ibm.com,
	christophe.leroy@csgroup.eu, naveen@kernel.org,
	maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	mykolal@fb.com, shuah@kernel.org, henriette.herzog@rub.de,
	skb99@linux.ibm.com, cupertino.miranda@oracle.com, mrpre@163.com,
	m.shachnai@gmail.com, dimitar.kanaliev@siteground.com,
	shung-hsi.yu@suse.com, dxu@dxuuu.xyz, bpf@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 00/11] bpf: Mitigate Spectre v1 using barriers
Date: Fri, 09 May 2025 18:40:30 +0000	[thread overview]
Message-ID: <174681603001.3715348.12288999798860158953.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250501073603.1402960-1-luis.gerhorst@fau.de>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu,  1 May 2025 09:35:51 +0200 you wrote:
> This improves the expressiveness of unprivileged BPF by inserting
> speculation barriers instead of rejecting the programs.
> 
> The approach was previously presented at LPC'24 [1] and RAID'24 [2].
> 
> To mitigate the Spectre v1 (PHT) vulnerability, the kernel rejects
> potentially-dangerous unprivileged BPF programs as of
> commit 9183671af6db ("bpf: Fix leakage under speculation on mispredicted
> branches"). In [2], we have analyzed 364 object files from open source
> projects (Linux Samples and Selftests, BCC, Loxilb, Cilium, libbpf
> Examples, Parca, and Prevail) and found that this affects 31% to 54% of
> programs.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,01/11] selftests/bpf: Fix caps for __xlated/jited_unpriv
    https://git.kernel.org/bpf/bpf-next/c/cf15cdc0f0f3
  - [bpf-next,v3,02/11] bpf: Move insn if/else into do_check_insn()
    (no matching commit)
  - [bpf-next,v3,03/11] bpf: Return -EFAULT on misconfigurations
    (no matching commit)
  - [bpf-next,v3,04/11] bpf: Return -EFAULT on internal errors
    (no matching commit)
  - [bpf-next,v3,05/11] bpf, arm64, powerpc: Add bpf_jit_bypass_spec_v1/v4()
    (no matching commit)
  - [bpf-next,v3,06/11] bpf, arm64, powerpc: Change nospec to include v1 barrier
    (no matching commit)
  - [bpf-next,v3,07/11] bpf: Rename sanitize_stack_spill to nospec_result
    (no matching commit)
  - [bpf-next,v3,08/11] bpf: Fall back to nospec for Spectre v1
    (no matching commit)
  - [bpf-next,v3,09/11] selftests/bpf: Add test for Spectre v1 mitigation
    (no matching commit)
  - [bpf-next,v3,10/11] bpf: Allow nospec-protected var-offset stack access
    (no matching commit)
  - [bpf-next,v3,11/11] bpf: Fall back to nospec for sanitization-failures
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




  parent reply	other threads:[~2025-05-09 18:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01  7:35 [PATCH bpf-next v3 00/11] bpf: Mitigate Spectre v1 using barriers Luis Gerhorst
2025-05-01  7:35 ` [PATCH bpf-next v3 01/11] selftests/bpf: Fix caps for __xlated/jited_unpriv Luis Gerhorst
2025-05-01 16:56   ` Kumar Kartikeya Dwivedi
2025-05-01 17:45   ` Eduard Zingerman
2025-05-01  7:35 ` [PATCH bpf-next v3 02/11] bpf: Move insn if/else into do_check_insn() Luis Gerhorst
2025-05-01 18:22   ` Eduard Zingerman
2025-05-05 18:31     ` Luis Gerhorst
2025-05-01 22:06   ` Kumar Kartikeya Dwivedi
2025-05-01  7:35 ` [PATCH bpf-next v3 03/11] bpf: Return -EFAULT on misconfigurations Luis Gerhorst
2025-05-01 22:06   ` Kumar Kartikeya Dwivedi
2025-05-01  7:35 ` [PATCH bpf-next v3 04/11] bpf: Return -EFAULT on internal errors Luis Gerhorst
2025-05-01 22:07   ` Kumar Kartikeya Dwivedi
2025-05-01  7:35 ` [PATCH bpf-next v3 05/11] bpf, arm64, powerpc: Add bpf_jit_bypass_spec_v1/v4() Luis Gerhorst
2025-05-01 22:14   ` Kumar Kartikeya Dwivedi
2025-05-18 10:38   ` Hari Bathini
2025-05-01  7:35 ` [PATCH bpf-next v3 06/11] bpf, arm64, powerpc: Change nospec to include v1 barrier Luis Gerhorst
2025-05-19  7:01   ` Hari Bathini
2025-05-01  7:35 ` [PATCH bpf-next v3 07/11] bpf: Rename sanitize_stack_spill to nospec_result Luis Gerhorst
2025-05-01 22:30   ` Kumar Kartikeya Dwivedi
2025-05-01  7:35 ` [PATCH bpf-next v3 08/11] bpf: Fall back to nospec for Spectre v1 Luis Gerhorst
2025-05-01 23:55   ` Kumar Kartikeya Dwivedi
2025-05-02 18:57     ` Luis Gerhorst
2025-05-14  5:38   ` Kumar Kartikeya Dwivedi
2025-05-01  7:36 ` [PATCH bpf-next v3 09/11] selftests/bpf: Add test for Spectre v1 mitigation Luis Gerhorst
2025-05-14  6:24   ` Kumar Kartikeya Dwivedi
2025-05-01  7:36 ` [PATCH bpf-next v3 10/11] bpf: Allow nospec-protected var-offset stack access Luis Gerhorst
2025-05-02  0:03   ` Kumar Kartikeya Dwivedi
2025-06-03 21:07     ` Luis Gerhorst
2025-05-14  6:28   ` Kumar Kartikeya Dwivedi
2025-05-01  7:36 ` [PATCH bpf-next v3 11/11] bpf: Fall back to nospec for sanitization-failures Luis Gerhorst
2025-05-14  6:47   ` Kumar Kartikeya Dwivedi
2025-05-14 17:30     ` Luis Gerhorst
2025-05-14 17:34       ` Kumar Kartikeya Dwivedi
2025-05-09 18:40 ` patchwork-bot+netdevbpf [this message]
2025-05-09 18:43   ` [PATCH bpf-next v3 00/11] bpf: Mitigate Spectre v1 using barriers 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=174681603001.3715348.12288999798860158953.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=christophe.leroy@csgroup.eu \
    --cc=cupertino.miranda@oracle.com \
    --cc=daniel@iogearbox.net \
    --cc=dimitar.kanaliev@siteground.com \
    --cc=dxu@dxuuu.xyz \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=hbathini@linux.ibm.com \
    --cc=henriette.herzog@rub.de \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luis.gerhorst@fau.de \
    --cc=m.shachnai@gmail.com \
    --cc=maddy@linux.ibm.com \
    --cc=martin.lau@linux.dev \
    --cc=mpe@ellerman.id.au \
    --cc=mrpre@163.com \
    --cc=mykolal@fb.com \
    --cc=naveen@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=puranjay@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=shung-hsi.yu@suse.com \
    --cc=skb99@linux.ibm.com \
    --cc=song@kernel.org \
    --cc=will@kernel.org \
    --cc=xukuohai@huaweicloud.com \
    --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;
as well as URLs for NNTP newsgroup(s).