BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, josef@toxicpanda.com,
	mason@kernel.org
Subject: Re: [PATCH bpf-next v3 00/16] bpf: Memory safety, lifetime and locking fixes (followups)
Date: Sun, 18 Oct 2026 00:50:09 +0000	[thread overview]
Message-ID: <179228460928.1496838.4730449210164481287.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261017230950.802052-1-alexei.starovoitov@gmail.com>

Hello:

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

On Sat, 17 Oct 2026 23:09:34 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> The first 30 patches of v2 are applied. This is the rest of the series,
> with what the reviews of v2 have found, and two fixes on top of patches
> that are applied already. Most of the patches are from Josef.
> 
> Every bug was reproduced in a VM on top of bpf-next, on the kernel right
> before and right after the patch that fixes it. The splats are in the
> commit logs. That goes for what the reviews have found as well.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,01/16] bpf: Don't take a program with a target program for an iterator
    https://git.kernel.org/bpf/bpf-next/c/b83bacf2161d
  - [bpf-next,v3,02/16] bpf: Don't let an extension reach further into the context than its target
    https://git.kernel.org/bpf/bpf-next/c/fcbfa99aa657
  - [bpf-next,v3,03/16] bpf: Keep values of a dead owner for sleepable programs
    https://git.kernel.org/bpf/bpf-next/c/f693030a187b
  - [bpf-next,v3,04/16] bpf: Don't take an extension for a function that runs sleepable
    https://git.kernel.org/bpf/bpf-next/c/b6458abbafe4
  - [bpf-next,v3,05/16] bpf: Keep the symbols of a program until it has ended
    https://git.kernel.org/bpf/bpf-next/c/4eaf4d71b91a
  - [bpf-next,v3,06/16] bpf: Use the socket of a sk_lookup test run under RCU
    https://git.kernel.org/bpf/bpf-next/c/6aff0129f327
  - [bpf-next,v3,07/16] bpf, cpumap: Hold the device of frames in the queue
    https://git.kernel.org/bpf/bpf-next/c/f99351272933
  - [bpf-next,v3,08/16] bpf: Drop packet pointers behind kfuncs writing an skb
    https://git.kernel.org/bpf/bpf-next/c/19e6ca6b4a22
  - [bpf-next,v3,09/16] bpf: Let bpf_dynptr_write() mark a global function
    https://git.kernel.org/bpf/bpf-next/c/589998616e0f
  - [bpf-next,v3,10/16] bpf: Don't take a dynptr argument for a local dynptr
    https://git.kernel.org/bpf/bpf-next/c/b7f97db88948
  - [bpf-next,v3,11/16] bpf: Refuse the prologue for an extension that cannot take it
    https://git.kernel.org/bpf/bpf-next/c/aa486cff4964
  - [bpf-next,v3,12/16] bpf: Unclone the skb for kfuncs that write through a dynptr
    https://git.kernel.org/bpf/bpf-next/c/bb72c2866831
  - [bpf-next,v3,13/16] bpf: Follow the head if an skb is written from a slice
    https://git.kernel.org/bpf/bpf-next/c/1c19f2b3b2f3
  - [bpf-next,v3,14/16] bpf: Use memmove() to store bytes in an skb
    https://git.kernel.org/bpf/bpf-next/c/1db084f42884
  - [bpf-next,v3,15/16] bpf: Use memmove() to store bytes in an xdp_buff
    https://git.kernel.org/bpf/bpf-next/c/ab08863c58b1
  - [bpf-next,v3,16/16] bpf: Refuse packet slices for packet-changing helpers
    https://git.kernel.org/bpf/bpf-next/c/a6f8a67c13dd

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



      parent reply	other threads:[~2026-10-18  0:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 23:09 [PATCH bpf-next v3 00/16] bpf: Memory safety, lifetime and locking fixes (followups) Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 01/16] bpf: Don't take a program with a target program for an iterator Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 02/16] bpf: Don't let an extension reach further into the context than its target Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 03/16] bpf: Keep values of a dead owner for sleepable programs Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 04/16] bpf: Don't take an extension for a function that runs sleepable Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 05/16] bpf: Keep the symbols of a program until it has ended Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 06/16] bpf: Use the socket of a sk_lookup test run under RCU Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 07/16] bpf, cpumap: Hold the device of frames in the queue Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 08/16] bpf: Drop packet pointers behind kfuncs writing an skb Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 09/16] bpf: Let bpf_dynptr_write() mark a global function Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 10/16] bpf: Don't take a dynptr argument for a local dynptr Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 11/16] bpf: Refuse the prologue for an extension that cannot take it Alexei Starovoitov
2026-10-17 23:29   ` sashiko-bot
2026-10-18  0:35     ` Alexei Starovoitov
2026-10-17 23:41   ` bot+bpf-ci
2026-10-17 23:09 ` [PATCH bpf-next v3 12/16] bpf: Unclone the skb for kfuncs that write through a dynptr Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 13/16] bpf: Follow the head if an skb is written from a slice Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 14/16] bpf: Use memmove() to store bytes in an skb Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 15/16] bpf: Use memmove() to store bytes in an xdp_buff Alexei Starovoitov
2026-10-17 23:09 ` [PATCH bpf-next v3 16/16] bpf: Refuse packet slices for packet-changing helpers Alexei Starovoitov
2026-10-18  0:50 ` 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=179228460928.1496838.4730449210164481287.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=josef@toxicpanda.com \
    --cc=mason@kernel.org \
    --cc=memxor@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