netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
	coreteam@netfilter.org
Subject: [nf-next:for-net-next3 37/40] net/netfilter/xt_addrtype.c:55: undefined reference to `nf_ip6_route'
Date: Wed, 20 Dec 2017 08:57:44 +0800	[thread overview]
Message-ID: <201712200842.dmz4G9Yk%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2551 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git for-net-next3
head:   dfbb1c16489ca1b93e3f8aebc74d9229f1d87cc6
commit: 4a61f6d1f4eddcb006e6d6ed1a90c81737c6dc0a [37/40] netfilter: remove route indirection in struct nf_afinfo
config: i386-randconfig-a1-12171902 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        git checkout 4a61f6d1f4eddcb006e6d6ed1a90c81737c6dc0a
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   net/netfilter/utils.o: In function `nf_checksum':
   net/netfilter/utils.c:18: undefined reference to `nf_ip6_checksum'
   net/netfilter/utils.o: In function `nf_checksum_partial':
   net/netfilter/utils.c:38: undefined reference to `nf_ip6_checksum_partial'
   net/netfilter/utils.o: In function `nf_saveroute':
   net/netfilter/utils.c:54: undefined reference to `nf_ip6_saveroute'
   net/netfilter/xt_addrtype.o: In function `match_lookup_rt6':
>> net/netfilter/xt_addrtype.c:55: undefined reference to `nf_ip6_route'
>> net/netfilter/xt_addrtype.c:55: undefined reference to `nf_ip6_route'

vim +55 net/netfilter/xt_addrtype.c

    34	
    35	#if IS_ENABLED(CONFIG_IP6_NF_IPTABLES)
    36	static u32 match_lookup_rt6(struct net *net, const struct net_device *dev,
    37				    const struct in6_addr *addr, u16 mask)
    38	{
    39		const struct nf_ipv6_ops *v6ops;
    40		struct flowi6 flow;
    41		struct rt6_info *rt;
    42		u32 ret = 0;
    43		int route_err;
    44	
    45		memset(&flow, 0, sizeof(flow));
    46		flow.daddr = *addr;
    47		if (dev)
    48			flow.flowi6_oif = dev->ifindex;
    49	
    50		if (dev && (mask & XT_ADDRTYPE_LOCAL)) {
    51			v6ops = nf_get_ipv6_ops();
    52			if (v6ops && v6ops->chk_addr(net, addr, dev, true))
    53				ret = XT_ADDRTYPE_LOCAL;
    54		}
  > 55		route_err = nf_ip6_route(net, (struct dst_entry **)&rt,
    56					 flowi6_to_flowi(&flow), false);
    57		if (route_err)
    58			return XT_ADDRTYPE_UNREACHABLE;
    59	
    60		if (rt->rt6i_flags & RTF_REJECT)
    61			ret = XT_ADDRTYPE_UNREACHABLE;
    62	
    63		if (dev == NULL && rt->rt6i_flags & RTF_LOCAL)
    64			ret |= XT_ADDRTYPE_LOCAL;
    65		if (ipv6_anycast_destination((struct dst_entry *)rt, addr))
    66			ret |= XT_ADDRTYPE_ANYCAST;
    67	
    68		dst_release(&rt->dst);
    69		return ret;
    70	}
    71	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31203 bytes --]

                 reply	other threads:[~2017-12-20  0:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201712200842.dmz4G9Yk%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=coreteam@netfilter.org \
    --cc=kbuild-all@01.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).