From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Hao Sun <sunhao.th@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: Fri, 15 Dec 2023 02:49:51 +0200 [thread overview]
Message-ID: <526d4ac8f6788d3323d29fdbad0e0e5d09a534db.camel@gmail.com> (raw)
In-Reply-To: <CAEf4BzYuV3odyj8A77ZW8H9jyx_YLhAkSiM+1hkvtH=OYcHL3w@mail.gmail.com>
On Thu, 2023-12-14 at 16:06 -0800, Andrii Nakryiko wrote:
[...]
> If you agree with the analysis, we can start discussing what's the
> best way to fix this.
Ok, yeap, I agree with you.
Backtracker marks both registers in 'if' statement if one of them is
tracked, but r8 is not marked at block entry and we miss r0.
next prev parent reply other threads:[~2023-12-15 0:49 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
2023-12-15 0:06 ` Andrii Nakryiko
2023-12-15 0:16 ` Eduard Zingerman
2023-12-15 0:49 ` Eduard Zingerman [this message]
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=526d4ac8f6788d3323d29fdbad0e0e5d09a534db.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