public inbox for bpf@vger.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, sunhao.th@gmail.com
Subject: Re: [bpf-next v3 0/4] bpf: track find_equal_scalars history on per-instruction level
Date: Fri, 19 Jul 2024 23:30:34 +0000	[thread overview]
Message-ID: <172143183410.24994.4836120843832681005.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240718202357.1746514-1-eddyz87@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Thu, 18 Jul 2024 13:23:52 -0700 you wrote:
> This is a fix for precision tracking bug reported in [0].
> It supersedes my previous attempt to fix similar issue in commit [1].
> Here is a minimized test case from [0]:
> 
>     0:  call bpf_get_prandom_u32;
>     1:  r7 = r0;
>     2:  r8 = r0;
>     3:  call bpf_get_prandom_u32;
>     4:  if r0 > 1 goto +0;
>     /* --- checkpoint #1: r7.id=1, r8.id=1 --- */
>     5:  if r8 >= r0 goto 9f;
>     6:  r8 += r8;
>     /* --- checkpoint #2: r7.id=1, r8.id=0 --- */
>     7:  if r7 == 0 goto 9f;
>     8:  r0 /= 0;
>     /* --- checkpoint #3 --- */
>     9:  r0 = 42;
>     10: exit;
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/4] bpf: track equal scalars history on per-instruction level
    https://git.kernel.org/bpf/bpf-next/c/2b7350d7ca65
  - [bpf-next,v3,2/4] bpf: remove mark_precise_scalar_ids()
    https://git.kernel.org/bpf/bpf-next/c/cb0f94d85874
  - [bpf-next,v3,3/4] selftests/bpf: tests for per-insn sync_linked_regs() precision tracking
    https://git.kernel.org/bpf/bpf-next/c/c0087d59e504
  - [bpf-next,v3,4/4] selftests/bpf: update comments find_equal_scalars->sync_linked_regs
    https://git.kernel.org/bpf/bpf-next/c/f081cd17c0bc

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



      parent reply	other threads:[~2024-07-19 23:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 20:23 [bpf-next v3 0/4] bpf: track find_equal_scalars history on per-instruction level Eduard Zingerman
2024-07-18 20:23 ` [bpf-next v3 1/4] bpf: track equal scalars " Eduard Zingerman
2024-07-19 23:27   ` Andrii Nakryiko
2024-07-18 20:23 ` [bpf-next v3 2/4] bpf: remove mark_precise_scalar_ids() Eduard Zingerman
2024-07-18 20:23 ` [bpf-next v3 3/4] selftests/bpf: tests for per-insn sync_linked_regs() precision tracking Eduard Zingerman
2024-07-18 20:23 ` [bpf-next v3 4/4] selftests/bpf: update comments find_equal_scalars->sync_linked_regs Eduard Zingerman
2024-07-19 23: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=172143183410.24994.4836120843832681005.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=sunhao.th@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox