From: Yonghong Song <yhs@fb.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, Martin KaFai Lau <kafai@fb.com>,
<linux-next@vger.kernel.org>
Subject: Re: [PATCH bpf-next] kernel/bpf/verifier: fix build when NET is not enabled
Date: Tue, 6 Oct 2020 23:12:05 -0700 [thread overview]
Message-ID: <fcf3f659-027e-517f-086d-deb3ad33d953@fb.com> (raw)
In-Reply-To: <20201007021613.13646-1-rdunlap@infradead.org>
On 10/6/20 7:16 PM, Randy Dunlap wrote:
> Fix build errors in kernel/bpf/verifier.c when CONFIG_NET is
> not enabled.
>
> ../kernel/bpf/verifier.c:3995:13: error: ‘btf_sock_ids’ undeclared here (not in a function); did you mean ‘bpf_sock_ops’?
> .btf_id = &btf_sock_ids[BTF_SOCK_TYPE_SOCK_COMMON],
>
> ../kernel/bpf/verifier.c:3995:26: error: ‘BTF_SOCK_TYPE_SOCK_COMMON’ undeclared here (not in a function); did you mean ‘PTR_TO_SOCK_COMMON’?
> .btf_id = &btf_sock_ids[BTF_SOCK_TYPE_SOCK_COMMON],
>
> Fixes: 1df8f55a37bd ("bpf: Enable bpf_skc_to_* sock casting helper to networking prog type")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: netdev@vger.kernel.org
> Cc: bpf@vger.kernel.org
> Cc: Martin KaFai Lau <kafai@fb.com>
> Cc: linux-next@vger.kernel.org
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2020-10-07 6:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 2:16 [PATCH bpf-next] kernel/bpf/verifier: fix build when NET is not enabled Randy Dunlap
2020-10-07 6:12 ` Yonghong Song [this message]
2020-10-07 18:00 ` patchwork-bot+netdevbpf
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=fcf3f659-027e-517f-086d-deb3ad33d953@fb.com \
--to=yhs@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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.