All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
	yonghong.song@linux.dev, memxor@gmail.com, npc@anthropic.com
Subject: Re: [PATCH bpf 1/2] bpf: don't downgrade half-dead scalar zero spills to STACK_ZERO
Date: Fri, 28 Aug 2026 17:50:06 +0000	[thread overview]
Message-ID: <178793940689.2709471.3309560614561309281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260827-bug-011-cleanfunc-stack-zero-simple-v1-v1-1-c0e996589a52@gmail.com>

Hello:

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

On Thu, 27 Aug 2026 15:48:23 -0700 you wrote:
> states.c:__clean_func_state() can downgrade scalar zero spill to
> STACK_ZERO in the following case:
> 
>   *(u64 *)(r10 - 8) = 0;
>   ... checkpoint ...
>   r1 = *(u32 *)(r10 - 4);
>   ... no reads from r10-8 ...
> 
> [...]

Here is the summary with links:
  - [bpf,1/2] bpf: don't downgrade half-dead scalar zero spills to STACK_ZERO
    https://git.kernel.org/bpf/bpf/c/2f3536bff882
  - [bpf,2/2] selftests/bpf: half-dead scalar zero stack spill test
    https://git.kernel.org/bpf/bpf/c/c6ff14f1cd9e

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-08-28 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 22:48 [PATCH bpf 1/2] bpf: don't downgrade half-dead scalar zero spills to STACK_ZERO Eduard Zingerman
2026-08-27 22:48 ` [PATCH bpf 2/2] selftests/bpf: half-dead scalar zero stack spill test Eduard Zingerman
2026-08-28 17: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=178793940689.2709471.3309560614561309281.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=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=npc@anthropic.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.