BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xu Yunxiang <xyx2021@mail.ustc.edu.cn>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
	sun.jian.kdev@gmail.com
Subject: Re: [PATCH bpf v2 0/2] bpf: Reject non-negative stack object offsets
Date: Mon, 21 Sep 2026 22:10:06 +0000	[thread overview]
Message-ID: <179002860614.3260819.5672763578696261726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260920210423.345636-1-xyx2021@mail.ustc.edu.cn>

Hello:

This series was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Mon, 21 Sep 2026 05:04:20 +0800 you wrote:
> Reject non-negative offsets before converting a stack object address to a
> stack slot index. Add a regression test for iterator destruction through
> fp+0.
> 
> Changes in v2:
> - Split the kernel change and selftest as requested by Andrii.
> - Rebase onto bpf/master at a11212910cf09b2fe8db9afa41ef60c4f81879c5.
> - Keep the original code and test changes unchanged and retain Sun Jian's
>   Reviewed-by on both parts.
> 
> [...]

Here is the summary with links:
  - [bpf,v2,1/2] bpf: Reject non-negative offsets in stack_slot_obj_get_spi()
    https://git.kernel.org/bpf/bpf/c/79a9172f3ab4
  - [bpf,v2,2/2] selftests/bpf: Reject iterator destruction through fp+0
    https://git.kernel.org/bpf/bpf/c/8244668cbbff

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-09-21 22:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20 21:04 [PATCH bpf v2 0/2] bpf: Reject non-negative stack object offsets Xu Yunxiang
2026-09-20 21:04 ` [PATCH bpf v2 1/2] bpf: Reject non-negative offsets in stack_slot_obj_get_spi() Xu Yunxiang
2026-09-20 21:04 ` [PATCH bpf v2 2/2] selftests/bpf: Reject iterator destruction through fp+0 Xu Yunxiang
2026-09-21 22:10 ` 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=179002860614.3260819.5672763578696261726.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=memxor@gmail.com \
    --cc=sun.jian.kdev@gmail.com \
    --cc=xyx2021@mail.ustc.edu.cn \
    /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