All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCHv2 ipsec-next 09/10] xfrm: interface: support IP6IP6 and IP6IP tunnels processing with .cb_handler
Date: Fri, 03 Jul 2020 07:54:54 +0800	[thread overview]
Message-ID: <202007030758.OQAC7CGY%lkp@intel.com> (raw)
In-Reply-To: <c13ffdfb739d487a415897b72bf8eee6981830c6.1593502515.git.lucien.xin@gmail.com>

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

Hi Xin,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on ipsec-next/master]

url:    https://github.com/0day-ci/linux/commits/Xin-Long/xfrm-support-ipip-and-ipv6-tunnels-in-vti-and-xfrmi/20200630-154042
base:   https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
config: x86_64-randconfig-a012-20200701 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: net/xfrm/xfrm_interface.o: in function `xfrmi6_rcv_tunnel':
>> net/xfrm/xfrm_interface.c:807: undefined reference to `xfrm6_tunnel_spi_lookup'

vim +807 net/xfrm/xfrm_interface.c

   800	
   801	static int xfrmi6_rcv_tunnel(struct sk_buff *skb)
   802	{
   803		const xfrm_address_t *saddr;
   804		__be32 spi;
   805	
   806		saddr = (const xfrm_address_t *)&ipv6_hdr(skb)->saddr;
 > 807		spi = xfrm6_tunnel_spi_lookup(dev_net(skb->dev), saddr);
   808	
   809		return xfrm6_rcv_spi(skb, IPPROTO_IPV6, spi, NULL);
   810	}
   811	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Xin Long <lucien.xin@gmail.com>, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org,
	Jakub Kicinski <jakub.kicinski@netronome.com>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [PATCHv2 ipsec-next 09/10] xfrm: interface: support IP6IP6 and IP6IP tunnels processing with .cb_handler
Date: Fri, 3 Jul 2020 07:54:54 +0800	[thread overview]
Message-ID: <202007030758.OQAC7CGY%lkp@intel.com> (raw)
In-Reply-To: <c13ffdfb739d487a415897b72bf8eee6981830c6.1593502515.git.lucien.xin@gmail.com>

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

Hi Xin,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on ipsec-next/master]

url:    https://github.com/0day-ci/linux/commits/Xin-Long/xfrm-support-ipip-and-ipv6-tunnels-in-vti-and-xfrmi/20200630-154042
base:   https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
config: x86_64-randconfig-a012-20200701 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: net/xfrm/xfrm_interface.o: in function `xfrmi6_rcv_tunnel':
>> net/xfrm/xfrm_interface.c:807: undefined reference to `xfrm6_tunnel_spi_lookup'

vim +807 net/xfrm/xfrm_interface.c

   800	
   801	static int xfrmi6_rcv_tunnel(struct sk_buff *skb)
   802	{
   803		const xfrm_address_t *saddr;
   804		__be32 spi;
   805	
   806		saddr = (const xfrm_address_t *)&ipv6_hdr(skb)->saddr;
 > 807		spi = xfrm6_tunnel_spi_lookup(dev_net(skb->dev), saddr);
   808	
   809		return xfrm6_rcv_spi(skb, IPPROTO_IPV6, spi, NULL);
   810	}
   811	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

  reply	other threads:[~2020-07-02 23:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  7:36 [PATCHv2 ipsec-next 00/10] xfrm: support ipip and ipv6 tunnels in vti and xfrmi Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 01/10] xfrm: add is_ipip to struct xfrm_input_afinfo Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 02/10] tunnel4: add cb_handler to struct xfrm_tunnel Xin Long
2020-07-02 20:46   ` kernel test robot
2020-07-02 20:46     ` kernel test robot
2020-07-02 20:53   ` kernel test robot
2020-07-02 20:53     ` kernel test robot
2020-07-05 18:30     ` Xin Long
2020-07-05 18:30       ` Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 03/10] tunnel6: add tunnel6_input_afinfo for ipip and ipv6 tunnels Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 04/10] ip_vti: support IPIP tunnel processing with .cb_handler Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 05/10] ip_vti: support IPIP6 tunnel processing Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 06/10] ip6_vti: support IP6IP6 tunnel processing with .cb_handler Xin Long
2020-07-02 22:20   ` kernel test robot
2020-07-02 22:20     ` kernel test robot
2020-07-02 23:33   ` kernel test robot
2020-07-02 23:33     ` kernel test robot
2020-07-05 16:57     ` Xin Long
2020-07-05 16:57       ` Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 07/10] ip6_vti: support IP6IP tunnel processing Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 08/10] ipcomp: assign if_id to child tunnel from parent tunnel Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 09/10] xfrm: interface: support IP6IP6 and IP6IP tunnels processing with .cb_handler Xin Long
2020-07-02 23:54   ` kernel test robot [this message]
2020-07-02 23:54     ` kernel test robot
2020-07-05 16:57     ` Xin Long
2020-07-05 16:57       ` Xin Long
2020-06-30  7:36 ` [PATCHv2 ipsec-next 10/10] xfrm: interface: support IPIP and IPIP6 " Xin Long

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=202007030758.OQAC7CGY%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.