From: Al Viro <viro@ZenIV.linux.org.uk>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>, mpe <mpe@ellerman.id.au>,
sachinp <sachinp@linux.vnet.ibm.com>
Subject: Re: [linux-next][41e83b9][gcc 4.8.5] make modules fail at net/netfilter/xt_bpf.ko
Date: Tue, 5 Dec 2017 18:06:50 +0000 [thread overview]
Message-ID: <20171205180650.GV21978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1512484991.13113.11.camel@abdul>
On Tue, Dec 05, 2017 at 08:13:11PM +0530, Abdul Haleem wrote:
> Hi Al Viro,
>
> Today's next kernel build failed with commit 41e83b9: fix "netfilter:
> xt_bpf: Fix XT_BPF_MODE_FD_PINNED
>
> Machine Type: Power 7
> kernel version: 4.15.0-rc2-next-20171204
> kernel config: attached
> test: 'make modules'
>
> ERROR: ".bpf_prog_get_type_path" [net/netfilter/xt_bpf.ko] undefined!
>
> Kernel built fine when bad commit is reverted.
In the same commit there's
+EXPORT_SYMBOL(bpf_prog_get_type_path);
so I really wonder WTF is going on...
Oh, I see. !BPF_SYSCALL and NETFILTER_XT_MATCH_BPF in .config triggers
that. Incremental (to be folded into the commit in question) follows:
diff --git a/include/linux/bpf.h b/include/linux/bpf.h
index a7000e4775e7..571450f98006 100644
--- a/include/linux/bpf.h
+++ b/include/linux/bpf.h
@@ -419,6 +419,8 @@ static inline int bpf_map_attr_numa_node(const union bpf_attr *attr)
attr->numa_node : NUMA_NO_NODE;
}
+struct bpf_prog *bpf_prog_get_type_path(const char *name, enum bpf_prog_type type);
+
#else /* !CONFIG_BPF_SYSCALL */
static inline struct bpf_prog *bpf_prog_get(u32 ufd)
{
@@ -506,6 +508,12 @@ static inline int cpu_map_enqueue(struct bpf_cpu_map_entry *rcpu,
{
return 0;
}
+
+static inline struct bpf_prog *bpf_prog_get_type_path(const char *name,
+ enum bpf_prog_type type)
+{
+ return -EOPNOTSUPP;
+}
#endif /* CONFIG_BPF_SYSCALL */
static inline struct bpf_prog *bpf_prog_get_type(u32 ufd,
@@ -514,7 +522,6 @@ static inline struct bpf_prog *bpf_prog_get_type(u32 ufd,
return bpf_prog_get_type_dev(ufd, type, false);
}
-struct bpf_prog *bpf_prog_get_type_path(const char *name, enum bpf_prog_type type);
bool bpf_prog_get_ok(struct bpf_prog *, enum bpf_prog_type *, bool);
int bpf_prog_offload_compile(struct bpf_prog *prog);
next prev parent reply other threads:[~2017-12-05 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 14:43 [linux-next][41e83b9][gcc 4.8.5] make modules fail at net/netfilter/xt_bpf.ko Abdul Haleem
2017-12-05 18:06 ` Al Viro [this message]
2017-12-06 10:26 ` [41e83b9][gcc " Abdul Haleem
2017-12-06 10:26 ` [linux-next][41e83b9][gcc " Abdul Haleem
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=20171205180650.GV21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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.