From: patchwork-bot+bpf@kernel.org
To: Hao Luo <haoluo@google.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, ast@kernel.org, andriin@fb.com,
daniel@iogearbox.net, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org
Subject: Re: [PATCH v3] selftests/bpf: Fix test_verifier after introducing resolve_pseudo_ldimm64
Date: Wed, 07 Oct 2020 03:20:03 +0000 [thread overview]
Message-ID: <160204080334.2587.12222243524671170166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201007022857.2791884-1-haoluo@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 6 Oct 2020 19:28:57 -0700 you wrote:
> Commit 4976b718c355 ("bpf: Introduce pseudo_btf_id") switched
> the order of check_subprogs() and resolve_pseudo_ldimm() in
> the verifier. Now an empty prog expects to see the error "last
> insn is not an the prog of a single invalid ldimm exit or jmp"
> instead, because the check for subprogs comes first. It's now
> pointless to validate that half of ldimm64 won't be the last
> instruction.
>
> [...]
Here is the summary with links:
- [v3] selftests/bpf: Fix test_verifier after introducing resolve_pseudo_ldimm64
https://git.kernel.org/bpf/bpf-next/c/bf88a80a0407
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:[~2020-10-07 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 2:28 [PATCH v3] selftests/bpf: Fix test_verifier after introducing resolve_pseudo_ldimm64 Hao Luo
2020-10-07 3:20 ` patchwork-bot+bpf [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=160204080334.2587.12222243524671170166.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bpf@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.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