From: patchwork-bot+netdevbpf@kernel.org
To: Jordan Rife <jrife@google.com>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, thinker.li@gmail.com, asavkov@redhat.com,
davemarchevsky@fb.com, imagedong@tencent.com, dxu@dxuuu.xyz,
void@manifault.com, daan.j.demeyer@gmail.com, bentiss@kernel.org,
houtao1@huawei.com, willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH v3 bpf-next 0/6] selftests/bpf: Add sockaddr tests for kernel networking
Date: Thu, 02 May 2024 22:30:31 +0000 [thread overview]
Message-ID: <171468903188.9823.10683400427580146706.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240429214529.2644801-1-jrife@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 29 Apr 2024 16:45:17 -0500 you wrote:
> This patch series adds test coverage for BPF sockaddr hooks and their
> interactions with kernel socket functions (i.e. kernel_bind(),
> kernel_connect(), kernel_sendmsg(), sock_sendmsg(),
> kernel_getpeername(), and kernel_getsockname()) while also rounding out
> IPv4 and IPv6 sockaddr hook coverage in prog_tests/sock_addr.c.
>
> As with v1 of this patch series, we add regression coverage for the
> issues addressed by these patches,
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/6] selftests/bpf: Fix bind program for big endian systems
https://git.kernel.org/bpf/bpf-next/c/8e667a065daa
- [v3,bpf-next,2/6] selftests/bpf: Implement socket kfuncs for bpf_testmod
https://git.kernel.org/bpf/bpf-next/c/bbb1cfdd0224
- [v3,bpf-next,3/6] selftests/bpf: Implement BPF programs for kernel socket operations
https://git.kernel.org/bpf/bpf-next/c/15b6671efa50
- [v3,bpf-next,4/6] selftests/bpf: Move IPv4 and IPv6 sockaddr test cases
https://git.kernel.org/bpf/bpf-next/c/8a9d22b8aeb2
- [v3,bpf-next,5/6] selftests/bpf: Make sock configurable for each test case
https://git.kernel.org/bpf/bpf-next/c/524e05ac4e14
- [v3,bpf-next,6/6] selftests/bpf: Add kernel socket operation tests
https://git.kernel.org/bpf/bpf-next/c/e0c8a7e7526f
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:[~2024-05-02 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 21:45 [PATCH v3 bpf-next 0/6] selftests/bpf: Add sockaddr tests for kernel networking Jordan Rife
2024-04-29 21:45 ` [PATCH v3 bpf-next 1/6] selftests/bpf: Fix bind program for big endian systems Jordan Rife
2024-04-29 21:45 ` [PATCH v3 bpf-next 2/6] selftests/bpf: Implement socket kfuncs for bpf_testmod Jordan Rife
2024-04-29 21:45 ` [PATCH v3 bpf-next 3/6] selftests/bpf: Implement BPF programs for kernel socket operations Jordan Rife
2024-04-29 21:45 ` [PATCH v3 bpf-next 4/6] selftests/bpf: Move IPv4 and IPv6 sockaddr test cases Jordan Rife
2024-04-29 21:45 ` [PATCH v3 bpf-next 5/6] selftests/bpf: Make sock configurable for each test case Jordan Rife
2024-04-29 21:45 ` [PATCH v3 bpf-next 6/6] selftests/bpf: Add kernel socket operation tests Jordan Rife
2024-05-02 22:30 ` 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=171468903188.9823.10683400427580146706.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=asavkov@redhat.com \
--cc=ast@kernel.org \
--cc=bentiss@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=imagedong@tencent.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jrife@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thinker.li@gmail.com \
--cc=void@manifault.com \
--cc=willemdebruijn.kernel@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).