diff options
| author | Andrii Nakryiko <andrii@kernel.org> | 2022-04-26 03:45:03 +0300 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2022-04-27 01:41:45 +0300 |
| commit | 0994a54c5202114ad0e3b3a0f1326e810b23ad38 (patch) | |
| tree | 4decce1af3e2f15077de5a15097e4153dae7cc87 | |
| parent | afe98d46ba22316acfd198eb5cd4db2ef2d427d7 (diff) | |
| download | linux-0994a54c5202114ad0e3b3a0f1326e810b23ad38.tar.xz | |
libbpf: Drop unhelpful "program too large" guess
libbpf pretends it knows actual limit of BPF program instructions based
on UAPI headers it compiled with. There is neither any guarantee that
UAPI headers match host kernel, nor BPF verifier actually uses
BPF_MAXINSNS constant anymore. Just drop unhelpful "guess", BPF verifier
will emit actual reason for failure in its logs anyways.
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Link: https://lore.kernel.org/bpf/20220426004511.2691730-3-andrii@kernel.org
| -rw-r--r-- | tools/lib/bpf/libbpf.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c index cc1a8fc47f72..b8cc862687a2 100644 --- a/tools/lib/bpf/libbpf.c +++ b/tools/lib/bpf/libbpf.c @@ -6828,10 +6828,6 @@ retry_load: pr_warn("prog '%s': -- BEGIN PROG LOAD LOG --\n%s-- END PROG LOAD LOG --\n", prog->name, log_buf); } - if (insns_cnt >= BPF_MAXINSNS) { - pr_warn("prog '%s': program too large (%d insns), at most %d insns\n", - prog->name, insns_cnt, BPF_MAXINSNS); - } out: if (own_log_buf) |