From: patchwork-bot+netdevbpf@kernel.org
To: Hao Sun <sunhao.th@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, john.fastabend@gmail.com,
memxor@gmail.com, martin.lau@linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/2] bpf: Fix uninit read for helper mem args on partially spilled slots
Date: Fri, 25 Sep 2026 10:00:05 +0000 [thread overview]
Message-ID: <179033040522.2428861.4397350193691349968.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925082814.1554771-1-sunhao.th@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Fri, 25 Sep 2026 10:28:13 +0200 you wrote:
> check_stack_range_initialized() takes the spilled register path when
> bpf_is_spilled_reg(ss) holds, which, however, only looks at the last
> byte of the slot. Hence, a partially spilled scalar (on the lower part)
> bypasses the check and the following loads:
>
> 0: (b7) r1 = 1 ; R1=1
> 1: (63) *(u32 *)(r10 -8) = r1 ; R1=1 R10=fp0 fp-8=????1
> 2: (18) r1 = 0x0 ; R1=map_ptr(map=rb,ks=0,vs=0)
> 4: (bf) r2 = r10 ; R2=fp0 R10=fp0
> 5: (07) r2 += -8 ; R2=fp-8
> 6: (b7) r3 = 8 ; R3=8
> 7: (b7) r4 = 0 ; R4=0
> 8: (85) call bpf_ringbuf_output#130
> ...
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Fix uninit read for helper mem args on partially spilled slots
https://git.kernel.org/bpf/bpf-next/c/b3861495d2b2
- [bpf-next,2/2] selftests/bpf: Test helper read of a narrow stack spill
https://git.kernel.org/bpf/bpf-next/c/7af653d4ebf8
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-09-25 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 8:28 Hao Sun
2026-09-25 8:28 ` [PATCH bpf-next 2/2] selftests/bpf: Test helper read of a narrow stack spill Hao Sun
2026-09-25 10:00 ` 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=179033040522.2428861.4397350193691349968.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=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sunhao.th@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
all inboxes | Powered by JetHome®