From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, songliubraving@fb.com, haoluo@google.com,
andrii@kernel.org, yhs@fb.com, ast@kernel.org,
daniel@iogearbox.net, kafai@fb.com, kpsingh@kernel.org,
davem@davemloft.net, kuba@kernel.org, sdf@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, oss@lmb.io,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next] bpf: Only add BTF IDs for socket security hooks when CONFIG_SECURITY_NETWORK is on
Date: Thu, 01 Sep 2022 23:30:15 +0000 [thread overview]
Message-ID: <166207501560.18006.8246668912607990725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220901065126.3856297-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 1 Sep 2022 14:51:26 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> When CONFIG_SECURITY_NETWORK is disabled, there will be build warnings
> from resolve_btfids:
>
> WARN: resolve_btfids: unresolved symbol bpf_lsm_socket_socketpair
> ......
> WARN: resolve_btfids: unresolved symbol bpf_lsm_inet_conn_established
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Only add BTF IDs for socket security hooks when CONFIG_SECURITY_NETWORK is on
https://git.kernel.org/bpf/bpf-next/c/ef331a8d4c00
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-09-01 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 6:51 [PATCH bpf-next] bpf: Only add BTF IDs for socket security hooks when CONFIG_SECURITY_NETWORK is on Hou Tao
2022-09-01 23: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=166207501560.18006.8246668912607990725.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=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=oss@lmb.io \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox