From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Alexis_Lothor=C3=A9_=3Calexis=2Elothore=40bootlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, memxor@gmail.com,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
shuah@kernel.org, ebpf@linuxfoundation.org,
bastien.curutchet@bootlin.com, thomas.petazzoni@bootlin.com,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: ignore call depth accounting for retbleed in verifier tests
Date: Thu, 04 Jun 2026 16:50:15 +0000 [thread overview]
Message-ID: <178059181541.2942053.15567465384217176140.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260528-fix_tests_for_retbleed_stuff-v1-1-c2022a1f3bee@bootlin.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 28 May 2026 15:27:14 +0200 you wrote:
> When running the selftests on a retbleed-affected platform (eg:
> Skylake), with call depth accounting enabled
> (CONFIG_CALL_DEPTH_TRACKING=y) _and_ with retbleed=stuff, some verifier
> selftests fail to validate the jited instructions. For example:
>
> MATCHED SUBSTR: ' endbr64'
> MATCHED SUBSTR: ' nopl (%rax,%rax)'
> MATCHED SUBSTR: ' xorq %rax, %rax'
> MATCHED SUBSTR: ' pushq %rbp'
> MATCHED SUBSTR: ' movq %rsp, %rbp'
> MATCHED SUBSTR: ' endbr64'
> MATCHED SUBSTR: ' cmpq $0x21, %rax'
> MATCHED SUBSTR: ' ja L0'
> MATCHED SUBSTR: ' pushq %rax'
> MATCHED SUBSTR: ' movq %rsp, %rax'
> MATCHED SUBSTR: ' jmp L1'
> MATCHED SUBSTR: 'L0: pushq %rax'
> MATCHED SUBSTR: 'L1: pushq %rax'
> MATCHED SUBSTR: ' movq -0x10(%rbp), %rax'
> WRONG LINE REGEX: ' callq 0x{{.*}}'
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: ignore call depth accounting for retbleed in verifier tests
https://git.kernel.org/bpf/bpf-next/c/bf29346fc393
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:[~2026-06-04 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 13:27 Alexis Lothoré (eBPF Foundation)
2026-06-02 0:45 ` Emil Tsalapatis
2026-06-04 16: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=178059181541.2942053.15567465384217176140.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Alexis_Lothor=C3=A9_=3Calexis=2Elothore=40bootlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ebpf@linuxfoundation.org \
--cc=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yonghong.song@linux.dev \
/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
Powered by JetHome