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, kuniyu@amazon.com
Subject: Re: [PATCH bpf v3 0/2] check bpf_func_state->callback_depth when pruning states
Date: Thu, 22 Feb 2024 17:10:27 +0000	[thread overview]
Message-ID: <170862182771.10220.3181097083078946216.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240222154121.6991-1-eddyz87@gmail.com>

Hello:

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

On Thu, 22 Feb 2024 17:41:19 +0200 you wrote:
> This patch-set fixes bug in states pruning logic hit in mailing list
> discussion [0]. The details of the fix are in patch #1.
> 
> The main idea for the fix belongs to Yonghong Song,
> mine contribution is merely in review and test cases.
> 
> There are some changes in verification performance:
> 
> [...]

Here is the summary with links:
  - [bpf,v3,1/2] bpf: check bpf_func_state->callback_depth when pruning states
    https://git.kernel.org/bpf/bpf/c/f31f0fe3d738
  - [bpf,v3,2/2] selftests/bpf: test case for callback_depth states pruning logic
    https://git.kernel.org/bpf/bpf/c/2861d07c5289

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-02-22 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 15:41 [PATCH bpf v3 0/2] check bpf_func_state->callback_depth when pruning states Eduard Zingerman
2024-02-22 15:41 ` [PATCH bpf v3 1/2] bpf: " Eduard Zingerman
2024-02-22 16:12   ` Yonghong Song
2024-02-22 15:41 ` [PATCH bpf v3 2/2] selftests/bpf: test case for callback_depth states pruning logic Eduard Zingerman
2024-02-22 17:10 ` 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=170862182771.10220.3181097083078946216.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=kuniyu@amazon.com \
    --cc=martin.lau@linux.dev \
    --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.