public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, andrii@kernel.org,
	song@kernel.org, haoluo@google.com, yhs@fb.com, ast@kernel.org,
	daniel@iogearbox.net, kpsingh@kernel.org, sdf@google.com,
	jolsa@kernel.org, john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next] bpf: Define sock security related BTF IDs under CONFIG_SECURITY_NETWORK
Date: Mon, 19 Dec 2022 21:10:18 +0000	[thread overview]
Message-ID: <167148421831.25912.620774133126350112.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221217062144.2507222-1-houtao@huaweicloud.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sat, 17 Dec 2022 14:21:44 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> There are warnings reported from resolve_btfids when building vmlinux
> with CONFIG_SECURITY_NETWORK disabled:
> 
>   WARN: resolve_btfids: unresolved symbol bpf_lsm_sk_free_security
>   WARN: resolve_btfids: unresolved symbol bpf_lsm_sk_alloc_security
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: Define sock security related BTF IDs under CONFIG_SECURITY_NETWORK
    https://git.kernel.org/bpf/bpf/c/cc074822465d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-12-19 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17  6:21 [PATCH bpf-next] bpf: Define sock security related BTF IDs under CONFIG_SECURITY_NETWORK Hou Tao
2022-12-17 16:25 ` Yonghong Song
2022-12-19 21:10 ` 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=167148421831.25912.620774133126350112.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=haoluo@google.com \
    --cc=houtao1@huawei.com \
    --cc=houtao@huaweicloud.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --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