From: Yonghong Song <yonghong.song@linux.dev>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: [PATCH bpf-next 2/3] bpf: Remove 'may_goto 0' instruction
Date: Wed, 15 Jan 2025 21:51:34 -0800 [thread overview]
Message-ID: <20250116055134.604867-1-yonghong.song@linux.dev> (raw)
In-Reply-To: <20250116055123.603790-1-yonghong.song@linux.dev>
Since 'may_goto 0' insns are actually no-op, let us remove them.
Otherwise, verifier will generate code like
/* r10 - 8 stores the implicit loop count */
r11 = *(u64 *)(r10 -8)
if r11 == 0x0 goto pc+2
r11 -= 1
*(u64 *)(r10 -8) = r11
which is the pure overhead.
The following code patterns (from the previous commit) are also
handled:
may_goto 2
may_goto 1
may_goto 0
With this commit, the above three 'may_goto' insns are all
eliminated.
Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
---
kernel/bpf/verifier.c | 36 ++++++++++++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index edf3cc42a220..72b474bfba2d 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -20133,6 +20133,40 @@ static int opt_remove_nops(struct bpf_verifier_env *env)
return 0;
}
+static int opt_remove_useless_may_gotos(struct bpf_verifier_env *env)
+{
+ struct bpf_insn *insn = env->prog->insnsi;
+ int i, j, err, last_may_goto, removed_cnt;
+ int insn_cnt = env->prog->len;
+
+ for (i = 0; i < insn_cnt; i++) {
+ if (!is_may_goto_insn(&insn[i]))
+ continue;
+
+ for (j = i + 1; j < insn_cnt; j++) {
+ if (!is_may_goto_insn(&insn[j]))
+ break;
+ }
+
+ last_may_goto = --j;
+ removed_cnt = 0;
+ while (j >= i) {
+ if (insn[j].off == 0) {
+ err = verifier_remove_insns(env, j, 1);
+ if (err)
+ return err;
+ removed_cnt++;
+ }
+ j--;
+ }
+
+ insn_cnt -= removed_cnt;
+ i = last_may_goto - removed_cnt;
+ }
+
+ return 0;
+}
+
static int opt_subreg_zext_lo32_rnd_hi32(struct bpf_verifier_env *env,
const union bpf_attr *attr)
{
@@ -23089,6 +23123,8 @@ int bpf_check(struct bpf_prog **prog, union bpf_attr *attr, bpfptr_t uattr, __u3
ret = opt_remove_dead_code(env);
if (ret == 0)
ret = opt_remove_nops(env);
+ if (ret == 0)
+ ret = opt_remove_useless_may_gotos(env);
} else {
if (ret == 0)
sanitize_dead_code(env);
--
2.43.5
next prev parent reply other threads:[~2025-01-16 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 5:51 [PATCH bpf-next 0/3] bpf: Allow 'may_goto 0' instruction Yonghong Song
2025-01-16 5:51 ` [PATCH bpf-next 1/3] " Yonghong Song
2025-01-16 19:23 ` Eduard Zingerman
2025-01-16 5:51 ` Yonghong Song [this message]
2025-01-16 19:42 ` [PATCH bpf-next 2/3] bpf: Remove " Eduard Zingerman
2025-01-17 1:45 ` Alexei Starovoitov
2025-01-17 3:43 ` Yonghong Song
2025-01-16 5:51 ` [PATCH bpf-next 3/3] selftests/bpf: Add some tests related to 'may_goto 0' insns Yonghong Song
2025-01-16 19:49 ` 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=20250116055134.604867-1-yonghong.song@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
/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