From: Michal Kubecek <mkubecek@suse.cz>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Yonghong Song <yhs@fb.com>
Subject: build failure (BTFIDS) with CONFIG_NET && !CONFIG_INET
Date: Tue, 29 Sep 2020 12:17:37 +0200 [thread overview]
Message-ID: <20200929101737.3ufw36bngkmzppqk@lion.mk-sys.cz> (raw)
Hello,
our builds of s390x for zfcpdump fail since 5.9-rc1 with
BTFIDS vmlinux
FAILED unresolved symbol tcp_timewait_sock
make[1]: *** [/home/abuild/rpmbuild/BUILD/kernel-zfcpdump-5.9.rc7/linux-5.9-rc7/Makefile:1176: vmlinux] Error 255
I believe this is caused by commit fce557bcef11 ("bpf: Make btf_sock_ids
global") and the problem is caused by a specific configuration which has
CONFIG_NET enabled but CONFIG_INET disabled. IIUC there will be no user
of struct tcp_timewait_sock but btf_ids will try to generate BTF info
for it.
Michal
next reply other threads:[~2020-09-29 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 10:17 Michal Kubecek [this message]
2020-09-30 4:57 ` build failure (BTFIDS) with CONFIG_NET && !CONFIG_INET Yonghong Song
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=20200929101737.3ufw36bngkmzppqk@lion.mk-sys.cz \
--to=mkubecek@suse.cz \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).