From: patchwork-bot+netdevbpf@kernel.org
To: Yiyang Chen <chenyy23@mails.tsinghua.edu.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
shuah@kernel.org, emil@etsalapatis.com, puranjay@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Reject arena frees below the arena base
Date: Sun, 19 Jul 2026 16:30:10 +0000 [thread overview]
Message-ID: <178447861014.2768115.6826703778150125984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260717-c10-031-public-bpf-next-v2-b4-v2-0-54b555443a7c@mails.tsinghua.edu.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Fri, 17 Jul 2026 12:53:46 +0000 you wrote:
> bpf_arena_free_pages() can be called with a scalar arena address. The
> runtime reconstructs a full user address from the arena base and the low
> 32 bits before returning the range to the arena free tree. A scalar one
> page below the arena base can otherwise produce an out-of-domain free-tree
> offset and make a later allocation return an address below the arena
> mapping.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Reject arena frees below the arena base
https://git.kernel.org/bpf/bpf-next/c/b5a71cb2db6d
- [bpf-next,v2,2/2] selftests/bpf: Cover scalar arena frees below the base
https://git.kernel.org/bpf/bpf-next/c/770b62a6d389
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-19 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 12:53 Yiyang Chen
2026-07-17 12:53 ` [PATCH bpf-next v2 1/2] " Yiyang Chen
2026-07-17 12:53 ` [PATCH bpf-next v2 2/2] selftests/bpf: Cover scalar arena frees below the base Yiyang Chen
2026-07-17 13:39 ` bot+bpf-ci
2026-07-19 16: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=178447861014.2768115.6826703778150125984.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=chenyy23@mails.tsinghua.edu.cn \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®