From: Eduard Zingerman <eddyz87@gmail.com>
To: Hao Sun <sunhao.th@gmail.com>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Bug Report] bpf: incorrectly pruning runtime execution path
Date: Thu, 14 Dec 2023 18:26:13 +0200 [thread overview]
Message-ID: <73d021e3f77161668aae833e478b210ed5cd2f4d.camel@gmail.com> (raw)
In-Reply-To: <9dee19c7d39795242c15b2f7aa56fb4a6c3ebffa.camel@gmail.com>
On Thu, 2023-12-14 at 17:10 +0200, Eduard Zingerman wrote:
> [...]
> > The reason why retval checks fails is that the way you disable dead
> > code removal pass is not complete. Disable opt_remove_dead_code()
> > just prevent the instruction #30 from being removed, but also note
> > opt_hard_wire_dead_code_branches(), which convert conditional jump
> > into unconditional one, so #30 is still skipped.
> >
> > > Note that I tried this test with two functions:
> > > - bpf_get_current_cgroup_id, with this function I get retval 2, not 4 :)
> > > - bpf_get_prandom_u32, with this function I get a random retval each time.
> > >
> > > What is the expectation when 'bpf_get_current_cgroup_id' is used?
> > > That it is some known (to us) number, but verifier treats it as unknown scalar?
> > >
> >
> > Either one would work, but to make #30 always taken, r0 should be
> > non-zero.
>
> Oh, thank you, I made opt_hard_wire_dead_code_branches() a noop,
> replaced r0 = 0x4 by r0 /= 0 and see "divide error: 0000 [#1] PREEMPT SMP NOPTI"
> error in the kernel log on every second or third run of the test
> (when using prandom).
>
> Working to minimize the test case will share results a bit later.
Here is the minimized version of the test:
https://gist.github.com/eddyz87/fb4d3c7d5aabdc2ae247ed73fefccd32
If executed several times: ./test_progs -vvv -a verifier_and/pruning_test
it eventually crashes VM with the following error:
[ 2.039066] divide error: 0000 [#1] PREEMPT SMP NOPTI
...
[ 2.039987] Call Trace:
[ 2.039987] <TASK>
[ 2.039987] ? die+0x36/0x90
[ 2.039987] ? do_trap+0xdb/0x100
[ 2.039987] ? bpf_prog_32cfdb2c00b08250_pruning_test+0x4d/0x60
[ 2.039987] ? do_error_trap+0x7d/0x110
[ 2.039987] ? bpf_prog_32cfdb2c00b08250_pruning_test+0x4d/0x60
[ 2.039987] ? exc_divide_error+0x38/0x50
[ 2.039987] ? bpf_prog_32cfdb2c00b08250_pruning_test+0x4d/0x60
[ 2.039987] ? asm_exc_divide_error+0x1a/0x20
[ 2.039987] ? bpf_prog_32cfdb2c00b08250_pruning_test+0x4d/0x60
[ 2.039987] bpf_test_run+0x1b5/0x350
[ 2.039987] ? bpf_test_run+0x115/0x350
...
I'll continue debugging this a bit later today.
next prev parent reply other threads:[~2023-12-14 16:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 15:31 [Bug Report] bpf: incorrectly pruning runtime execution path Hao Sun
2023-12-13 0:51 ` Andrii Nakryiko
2023-12-13 10:25 ` Hao Sun
2023-12-13 23:30 ` Andrii Nakryiko
2023-12-14 0:08 ` Eduard Zingerman
2023-12-14 0:36 ` Andrii Nakryiko
2023-12-13 23:35 ` Eduard Zingerman
2023-12-13 23:40 ` Andrii Nakryiko
2023-12-13 23:47 ` Eduard Zingerman
2023-12-13 23:50 ` Andrii Nakryiko
2023-12-14 9:38 ` Hao Sun
2023-12-14 15:10 ` Eduard Zingerman
2023-12-14 16:26 ` Eduard Zingerman [this message]
2023-12-15 0:06 ` Andrii Nakryiko
2023-12-15 0:16 ` Eduard Zingerman
2023-12-15 0:49 ` Eduard Zingerman
2023-12-15 1:24 ` Eduard Zingerman
2023-12-15 1:43 ` Eduard Zingerman
2023-12-15 2:16 ` Alexei Starovoitov
2023-12-15 2:28 ` Eduard Zingerman
2023-12-15 5:20 ` Andrii Nakryiko
2023-12-15 16:22 ` Eduard Zingerman
2023-12-15 17:01 ` Andrii Nakryiko
2023-12-15 20:55 ` 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=73d021e3f77161668aae833e478b210ed5cd2f4d.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sunhao.th@gmail.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