BPF List
 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, awerner32@gmail.com,
	john.fastabend@gmail.com
Subject: Re: [PATCH bpf-next v3 0/7] exact states comparison for iterator convergence checks
Date: Tue, 24 Oct 2023 05:10:23 +0000	[thread overview]
Message-ID: <169812422398.23324.8361385101947039883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231024000917.12153-1-eddyz87@gmail.com>

Hello:

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

On Tue, 24 Oct 2023 03:09:10 +0300 you wrote:
> Iterator convergence logic in is_state_visited() uses state_equals()
> for states with branches counter > 0 to check if iterator based loop
> converges. This is not fully correct because state_equals() relies on
> presence of read and precision marks on registers. These marks are not
> guaranteed to be finalized while state has branches.
> Commit message for patch #3 describes a program that exhibits such
> behavior.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/7] bpf: move explored_state() closer to the beginning of verifier.c
    https://git.kernel.org/bpf/bpf-next/c/3c4e420cb653
  - [bpf-next,v3,2/7] bpf: extract same_callsites() as utility function
    https://git.kernel.org/bpf/bpf-next/c/4c97259abc9b
  - [bpf-next,v3,3/7] bpf: exact states comparison for iterator convergence checks
    https://git.kernel.org/bpf/bpf-next/c/2793a8b015f7
  - [bpf-next,v3,4/7] selftests/bpf: tests with delayed read/precision makrs in loop body
    https://git.kernel.org/bpf/bpf-next/c/389ede06c297
  - [bpf-next,v3,5/7] bpf: correct loop detection for iterators convergence
    https://git.kernel.org/bpf/bpf-next/c/2a0992829ea3
  - [bpf-next,v3,6/7] selftests/bpf: test if state loops are detected in a tricky case
    https://git.kernel.org/bpf/bpf-next/c/64870feebecb
  - [bpf-next,v3,7/7] bpf: print full verifier states on infinite loop detection
    https://git.kernel.org/bpf/bpf-next/c/b4d8239534fd

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



  parent reply	other threads:[~2023-10-24  5:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  0:09 [PATCH bpf-next v3 0/7] exact states comparison for iterator convergence checks Eduard Zingerman
2023-10-24  0:09 ` [PATCH bpf-next v3 1/7] bpf: move explored_state() closer to the beginning of verifier.c Eduard Zingerman
2023-10-24  0:09 ` [PATCH bpf-next v3 2/7] bpf: extract same_callsites() as utility function Eduard Zingerman
2023-10-24  0:09 ` [PATCH bpf-next v3 3/7] bpf: exact states comparison for iterator convergence checks Eduard Zingerman
2023-10-24  0:09 ` [PATCH bpf-next v3 4/7] selftests/bpf: tests with delayed read/precision makrs in loop body Eduard Zingerman
2023-10-24  1:43   ` kernel test robot
2023-10-24  0:09 ` [PATCH bpf-next v3 5/7] bpf: correct loop detection for iterators convergence Eduard Zingerman
2023-10-24  0:09 ` [PATCH bpf-next v3 6/7] selftests/bpf: test if state loops are detected in a tricky case Eduard Zingerman
2023-10-24  0:09 ` [PATCH bpf-next v3 7/7] bpf: print full verifier states on infinite loop detection Eduard Zingerman
2023-10-24  5:10 ` patchwork-bot+netdevbpf [this message]
2023-10-24  5:58 ` [PATCH bpf-next v3 0/7] exact states comparison for iterator convergence checks Andrii Nakryiko
2023-10-24 11:57   ` Eduard Zingerman

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=169812422398.23324.8361385101947039883.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=awerner32@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@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