BPF List
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: Geliang Tang <geliang.tang@suse.com>,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	mptcp@lists.linux.dev,
	Mat Martineau <mathew.j.martineau@linux.intel.com>
Subject: [PATCH bpf-next v4 2/7] selftests/bpf: Enable CONFIG_IKCONFIG_PROC in config
Date: Fri, 13 May 2022 15:48:22 -0700	[thread overview]
Message-ID: <20220513224827.662254-3-mathew.j.martineau@linux.intel.com> (raw)
In-Reply-To: <20220513224827.662254-1-mathew.j.martineau@linux.intel.com>

From: Geliang Tang <geliang.tang@suse.com>

CONFIG_IKCONFIG_PROC is required by BPF selftests, otherwise we get
errors like this:

 libbpf: failed to open system Kconfig
 libbpf: failed to load object 'kprobe_multi'
 libbpf: failed to load BPF skeleton 'kprobe_multi': -22

It's because /proc/config.gz is opened in bpf_object__read_kconfig_file()
in tools/lib/bpf/libbpf.c:

        file = gzopen("/proc/config.gz", "r");

So this patch enables CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC in
tools/testing/selftests/bpf/config.

Suggested-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Acked-by: Andrii Nakryiko <andrii@kernel.org>
Signed-off-by: Geliang Tang <geliang.tang@suse.com>
Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
---
 tools/testing/selftests/bpf/config | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tools/testing/selftests/bpf/config b/tools/testing/selftests/bpf/config
index 08c6e5a66d87..6840d4625e01 100644
--- a/tools/testing/selftests/bpf/config
+++ b/tools/testing/selftests/bpf/config
@@ -54,3 +54,5 @@ CONFIG_NF_DEFRAG_IPV6=y
 CONFIG_NF_CONNTRACK=y
 CONFIG_USERFAULTFD=y
 CONFIG_FPROBE=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
-- 
2.36.1


  parent reply	other threads:[~2022-05-13 22:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 22:48 [PATCH bpf-next v4 0/7] bpf: mptcp: Support for mptcp_sock Mat Martineau
2022-05-13 22:48 ` [PATCH bpf-next v4 1/7] bpf: add bpf_skc_to_mptcp_sock_proto Mat Martineau
2022-05-17  1:07   ` Martin KaFai Lau
2022-05-17  5:26     ` Geliang Tang
2022-05-17 17:00       ` Alexei Starovoitov
2022-05-19  0:38         ` Mat Martineau
2022-05-19 17:58           ` Martin KaFai Lau
2022-05-13 22:48 ` Mat Martineau [this message]
2022-05-13 22:48 ` [PATCH bpf-next v4 3/7] selftests/bpf: add MPTCP test base Mat Martineau
2022-05-16 22:43   ` Andrii Nakryiko
2022-05-17  5:30     ` Geliang Tang
2022-05-17  1:18   ` Martin KaFai Lau
2022-05-17  5:28     ` Geliang Tang
2022-05-13 22:48 ` [PATCH bpf-next v4 4/7] selftests/bpf: test bpf_skc_to_mptcp_sock Mat Martineau
2022-05-13 23:53   ` Geliang Tang
2022-05-16 22:47   ` Andrii Nakryiko
2022-05-17  1:20   ` Martin KaFai Lau
2022-05-17  5:29     ` Geliang Tang
2022-05-13 22:48 ` [PATCH bpf-next v4 5/7] selftests/bpf: verify token of struct mptcp_sock Mat Martineau
2022-05-16 22:45   ` Andrii Nakryiko
2022-05-17  1:32   ` Martin KaFai Lau
2022-05-17  5:19     ` Geliang Tang
2022-05-17 21:30       ` Martin KaFai Lau
2022-05-13 22:48 ` [PATCH bpf-next v4 6/7] selftests/bpf: verify ca_name " Mat Martineau
2022-05-13 22:48 ` [PATCH bpf-next v4 7/7] selftests/bpf: verify first " Mat Martineau

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=20220513224827.662254-3-mathew.j.martineau@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=geliang.tang@suse.com \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox