BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: eddyz87@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: Clear scalar delta on narrowing stack spill
Date: Fri, 11 Sep 2026 00:00:11 +0000	[thread overview]
Message-ID: <178908481113.2150752.7791376548198456287.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910185604.44949-1-daniel@iogearbox.net>

Hello:

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

On Thu, 10 Sep 2026 20:56:04 +0200 you wrote:
> check_stack_write_fixed_off() breaks the scalar link on a narrowing spill
> by zeroing the id of the destination stack slot, but leaves the delta in
> place. save_register_state() has just copied the source register verbatim,
> so the slot keeps the BPF_ADD_CONST delta of a register it is no longer
> linked to. This is the same shape as the case addressed in 1b327732c846
> ("bpf: Clear delta when clearing reg id for non-{add,sub} ops"). Unlike
> the latter, no miscomputation seems reachable, so mainly consistency.
> 
> [...]

Here is the summary with links:
  - [bpf] bpf: Clear scalar delta on narrowing stack spill
    https://git.kernel.org/bpf/bpf/c/2936aed9b021

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-11  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 18:56 [PATCH bpf] bpf: Clear scalar delta on narrowing stack spill Daniel Borkmann
2026-09-10 19:15 ` Eduard Zingerman
2026-09-11  0: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=178908481113.2150752.7791376548198456287.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@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