From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com,
kernel-team@fb.com, sdf@google.com
Subject: Re: [PATCH v2 bpf-next 0/3] Remove libcap dependency from bpf selftests
Date: Wed, 16 Mar 2022 22:20:11 +0000 [thread overview]
Message-ID: <164746921143.11329.12401305118912926154.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220316173816.2035581-1-kafai@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 16 Mar 2022 10:38:16 -0700 you wrote:
> After upgrading to the newer libcap (>= 2.60),
> the libcap commit aca076443591 ("Make cap_t operations thread safe.")
> added a "__u8 mutex;" to the "struct _cap_struct". It caused a few byte
> shift that breaks the assumption made in the "struct libcap" definition
> in test_verifier.c.
>
> This set is to remove the libcap dependency from the bpf selftests.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/3] bpf: selftests: Add helpers to directly use the capget and capset syscall
https://git.kernel.org/bpf/bpf-next/c/663af70aabb7
- [v2,bpf-next,2/3] bpf: selftests: Remove libcap usage from test_verifier
https://git.kernel.org/bpf/bpf-next/c/b1c2768a82b9
- [v2,bpf-next,3/3] bpf: selftests: Remove libcap usage from test_progs
https://git.kernel.org/bpf/bpf-next/c/82cb2b30773e
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:[~2022-03-16 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 17:38 [PATCH v2 bpf-next 0/3] Remove libcap dependency from bpf selftests Martin KaFai Lau
2022-03-16 17:38 ` [PATCH v2 bpf-next 1/3] bpf: selftests: Add helpers to directly use the capget and capset syscall Martin KaFai Lau
2022-03-16 17:38 ` [PATCH v2 bpf-next 2/3] bpf: selftests: Remove libcap usage from test_verifier Martin KaFai Lau
2022-03-16 17:38 ` [PATCH v2 bpf-next 3/3] bpf: selftests: Remove libcap usage from test_progs Martin KaFai Lau
2022-03-16 22:20 ` 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=164746921143.11329.12401305118912926154.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=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=sdf@google.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.