From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix verifier_private_stack test failure
Date: Mon, 31 Mar 2025 04:00:33 +0000 [thread overview]
Message-ID: <174339363328.3671970.15555565857872714950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250331033828.365077-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 30 Mar 2025 20:38:28 -0700 you wrote:
> Several verifier_private_stack tests failed with latest bpf-next.
> For example, for 'Private stack, single prog' subtest, the
> jitted code:
> func #0:
> 0: f3 0f 1e fa endbr64
> 4: 0f 1f 44 00 00 nopl (%rax,%rax)
> 9: 0f 1f 00 nopl (%rax)
> c: 55 pushq %rbp
> d: 48 89 e5 movq %rsp, %rbp
> 10: f3 0f 1e fa endbr64
> 14: 49 b9 58 74 8a 8f 7d 60 00 00 movabsq $0x607d8f8a7458, %r9
> 1e: 65 4c 03 0c 25 28 c0 48 87 addq %gs:-0x78b73fd8, %r9
> 27: bf 2a 00 00 00 movl $0x2a, %edi
> 2c: 49 89 b9 00 ff ff ff movq %rdi, -0x100(%r9)
> 33: 31 c0 xorl %eax, %eax
> 35: c9 leave
> 36: e9 20 5d 0f e1 jmp 0xffffffffe10f5d5b
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Fix verifier_private_stack test failure
https://git.kernel.org/bpf/bpf/c/07be1f644ff9
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:[~2025-03-31 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 3:38 [PATCH bpf-next] selftests/bpf: Fix verifier_private_stack test failure Yonghong Song
2025-03-31 4:00 ` 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=174339363328.3671970.15555565857872714950.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=martin.lau@kernel.org \
--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