public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com
Subject: Re: [PATCH bpf-next] bpf: remove unused insn_cnt argument from visit_[func_call_]insn()
Date: Wed, 07 Dec 2022 22:00:17 +0000	[thread overview]
Message-ID: <167045041761.21470.7399425333559579490.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221207195534.2866030-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed, 7 Dec 2022 11:55:34 -0800 you wrote:
> Number of total instructions in BPF program (including subprogs) can and
> is accessed from env->prog->len. visit_func_call_insn() doesn't do any
> checks against insn_cnt anymore, relying on push_insn() to do this check
> internally. So remove unnecessary insn_cnt input argument from
> visit_func_call_insn() and visit_insn() functions.
> 
> Suggested-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: remove unused insn_cnt argument from visit_[func_call_]insn()
    https://git.kernel.org/bpf/bpf-next/c/dcb2288b1fd9

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



      reply	other threads:[~2022-12-07 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 19:55 [PATCH bpf-next] bpf: remove unused insn_cnt argument from visit_[func_call_]insn() Andrii Nakryiko
2022-12-07 22: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=167045041761.21470.7399425333559579490.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=kernel-team@fb.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