BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, kkd@meta.com, ast@kernel.org,
	andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
	eddyz87@gmail.com, tao.lyu@epfl.ch, mathias.payer@nebelwelt.net,
	meng.xu.cs@uwaterloo.ca, sanidhya.kashyap@epfl.ch,
	kernel-team@fb.com
Subject: Re: [PATCH bpf v4 0/5] Fixes for stack with allow_ptr_leaks
Date: Wed, 04 Dec 2024 17:30:33 +0000	[thread overview]
Message-ID: <173333343351.1277728.7087223586728486550.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241204044757.1483141-1-memxor@gmail.com>

Hello:

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

On Tue,  3 Dec 2024 20:47:52 -0800 you wrote:
> Two fixes for usability/correctness gaps when interacting with the stack
> without CAP_PERFMON (i.e. with allow_ptr_leaks = false). See the commits
> for details. I've verified that the tests fail when run without the fixes.
> 
> Changelog:
> ----------
> v3 -> v4
> v3: https://lore.kernel.org/bpf/20241202083814.1888784-1-memxor@gmail.com
> 
> [...]

Here is the summary with links:
  - [bpf,v4,1/5] bpf: Don't mark STACK_INVALID as STACK_MISC in mark_stack_slot_misc
    https://git.kernel.org/bpf/bpf/c/69772f509e08
  - [bpf,v4,2/5] bpf: Fix narrow scalar spill onto 64-bit spilled scalar slots
    https://git.kernel.org/bpf/bpf/c/b0e66977dc07
  - [bpf,v4,3/5] selftests/bpf: Introduce __caps_unpriv annotation for tests
    https://git.kernel.org/bpf/bpf/c/adfdd9c68566
  - [bpf,v4,4/5] selftests/bpf: Add test for reading from STACK_INVALID slots
    https://git.kernel.org/bpf/bpf/c/f513c3635078
  - [bpf,v4,5/5] selftests/bpf: Add test for narrow spill into 64-bit spilled scalar
    https://git.kernel.org/bpf/bpf/c/19b6dbc006ec

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



      parent reply	other threads:[~2024-12-04 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  4:47 [PATCH bpf v4 0/5] Fixes for stack with allow_ptr_leaks Kumar Kartikeya Dwivedi
2024-12-04  4:47 ` [PATCH bpf v4 1/5] bpf: Don't mark STACK_INVALID as STACK_MISC in mark_stack_slot_misc Kumar Kartikeya Dwivedi
2024-12-04  4:47 ` [PATCH bpf v4 2/5] bpf: Fix narrow scalar spill onto 64-bit spilled scalar slots Kumar Kartikeya Dwivedi
2024-12-04  4:47 ` [PATCH bpf v4 3/5] selftests/bpf: Introduce __caps_unpriv annotation for tests Kumar Kartikeya Dwivedi
2024-12-04  4:47 ` [PATCH bpf v4 4/5] selftests/bpf: Add test for reading from STACK_INVALID slots Kumar Kartikeya Dwivedi
2024-12-04  4:47 ` [PATCH bpf v4 5/5] selftests/bpf: Add test for narrow spill into 64-bit spilled scalar Kumar Kartikeya Dwivedi
2024-12-04 17:30 ` 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=173333343351.1277728.7087223586728486550.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=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=kkd@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=mathias.payer@nebelwelt.net \
    --cc=memxor@gmail.com \
    --cc=meng.xu.cs@uwaterloo.ca \
    --cc=sanidhya.kashyap@epfl.ch \
    --cc=tao.lyu@epfl.ch \
    /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