From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com,
pizhenwei@bytedance.com
Subject: Re: [PATCH bpf-next v2] selftests/bpf: add a verifier scale test with unknown bounded loop
Date: Thu, 04 Mar 2021 15:50:07 +0000 [thread overview]
Message-ID: <161487300726.23414.8497936169085676798.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210226223810.236472-1-yhs@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 26 Feb 2021 14:38:10 -0800 you wrote:
> The original bcc pull request
> https://github.com/iovisor/bcc/pull/3270
> exposed a verifier failure with Clang 12/13 while
> Clang 4 works fine. Further investigation exposed two issues.
> Issue 1: LLVM may generate code which uses less refined
> value. The issue is fixed in llvm patch
> https://reviews.llvm.org/D97479
> Issue 2: Spills with initial value 0 are marked as precise
> which makes later state pruning less effective.
> This is my rough initial analysis and further investigation
> is needed to find how to improve verifier pruning
> in such cases.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: add a verifier scale test with unknown bounded loop
https://git.kernel.org/bpf/bpf-next/c/86a35af628e5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-04 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 22:38 [PATCH bpf-next v2] selftests/bpf: add a verifier scale test with unknown bounded loop Yonghong Song
2021-03-04 15:50 ` 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=161487300726.23414.8497936169085676798.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 \
--cc=pizhenwei@bytedance.com \
--cc=yhs@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