public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: KaFai Wan <kafai.wan@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
	sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
	shuah@kernel.org, paul.chaignon@gmail.com, m.shachnai@gmail.com,
	harishankar.vishwanathan@gmail.com, colin.i.king@gmail.com,
	luis.gerhorst@fau.de, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 0/2] bpf: Skip bounds adjustment for conditional jumps on same scalar register
Date: Tue, 04 Nov 2025 02:00:17 +0000	[thread overview]
Message-ID: <176222161773.2291263.14482517778610810582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251103063108.1111764-1-kafai.wan@linux.dev>

Hello:

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

On Mon,  3 Nov 2025 14:31:06 +0800 you wrote:
> This small patchset is about avoid verifier bug warning when conditional
>  jumps on same register when the register holds a scalar with range.
> 
> v4:
>   - make code better. (Alexei)
> 
> v3:
>   https://lore.kernel.org/bpf/20251031154107.403054-1-kafai.wan@linux.dev/
>   - Enhance is_scalar_branch_taken() to handle scalar case. (Eduard)
>   - Update the selftest to cover all conditional jump opcodes. (Eduard)
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/2] bpf: Skip bounds adjustment for conditional jumps on same scalar register
    https://git.kernel.org/bpf/bpf-next/c/d43ad9da8052
  - [bpf-next,v4,2/2] selftests/bpf: Add test for conditional jumps on same scalar register
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-04  2:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  6:31 [PATCH bpf-next v4 0/2] bpf: Skip bounds adjustment for conditional jumps on same scalar register KaFai Wan
2025-11-03  6:31 ` [PATCH bpf-next v4 1/2] " KaFai Wan
2025-11-03 18:09   ` Eduard Zingerman
2025-11-03  6:31 ` [PATCH bpf-next v4 2/2] selftests/bpf: Add test " KaFai Wan
2025-11-03 18:14   ` Eduard Zingerman
2025-11-04  1:55     ` Alexei Starovoitov
2025-11-04  2: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=176222161773.2291263.14482517778610810582.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=colin.i.king@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=harishankar.vishwanathan@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai.wan@linux.dev \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luis.gerhorst@fau.de \
    --cc=m.shachnai@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=paul.chaignon@gmail.com \
    --cc=sdf@fomichev.me \
    --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