From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul.chaignon@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org
Subject: Re: [PATCH bpf-next 1/2] selftests/bpf: Negative test case for ref_obj_id in args
Date: Wed, 02 Jul 2025 15:50:07 +0000 [thread overview]
Message-ID: <175147140777.772127.1115343254755259836.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <3ba78e6cda47ccafd6ea70dadbc718d020154664.1751463262.git.paul.chaignon@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 2 Jul 2025 15:53:23 +0200 you wrote:
> This patch adds a test case, as shown below, for the verifier error
> "more than one arg with ref_obj_id".
>
> 0: (b7) r2 = 20
> 1: (b7) r3 = 0
> 2: (18) r1 = 0xffff92cee3cbc600
> 4: (85) call bpf_ringbuf_reserve#131
> 5: (55) if r0 == 0x0 goto pc+3
> 6: (bf) r1 = r0
> 7: (bf) r2 = r0
> 8: (85) call bpf_tcp_raw_gen_syncookie_ipv4#204
> 9: (95) exit
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] selftests/bpf: Negative test case for ref_obj_id in args
https://git.kernel.org/bpf/bpf-next/c/1f2dfde4f36f
- [bpf-next,2/2] bpf: Avoid warning on multiple referenced args in call
https://git.kernel.org/bpf/bpf-next/c/564606fec540
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-07-02 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 13:53 [PATCH bpf-next 1/2] selftests/bpf: Negative test case for ref_obj_id in args Paul Chaignon
2025-07-02 13:54 ` [PATCH bpf-next 2/2] bpf: Avoid warning on multiple referenced args in call Paul Chaignon
2025-07-02 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=175147140777.772127.1115343254755259836.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=paul.chaignon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.