From: kernel test robot <lkp@intel.com>
To: Eyal Birger <eyal.birger@gmail.com>,
davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, pablo@netfilter.org, paul@nohats.ca,
nharold@google.com
Cc: oe-kbuild-all@lists.linux.dev, devel@linux-ipsec.org,
netdev@vger.kernel.org, Eyal Birger <eyal.birger@gmail.com>
Subject: Re: [PATCH ipsec-next,v2] xfrm: support sending NAT keepalives in ESP in UDP states
Date: Fri, 15 Dec 2023 02:51:11 +0800 [thread overview]
Message-ID: <202312150227.iYQMDIJT-lkp@intel.com> (raw)
In-Reply-To: <20231210180116.1737411-1-eyal.birger@gmail.com>
Hi Eyal,
kernel test robot noticed the following build errors:
[auto build test ERROR on netfilter-nf/main]
[also build test ERROR on linus/master v6.7-rc5 next-20231214]
[cannot apply to horms-ipvs/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Eyal-Birger/xfrm-support-sending-NAT-keepalives-in-ESP-in-UDP-states/20231211-020238
base: git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git main
patch link: https://lore.kernel.org/r/20231210180116.1737411-1-eyal.birger%40gmail.com
patch subject: [PATCH ipsec-next,v2] xfrm: support sending NAT keepalives in ESP in UDP states
config: x86_64-rhel-8.3-ltp (https://download.01.org/0day-ci/archive/20231215/202312150227.iYQMDIJT-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231215/202312150227.iYQMDIJT-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312150227.iYQMDIJT-lkp@intel.com/
All errors (new ones prefixed by >>):
net/xfrm/xfrm_nat_keepalive.c: In function 'nat_keepalive_send_ipv6':
>> net/xfrm/xfrm_nat_keepalive.c:78:21: error: implicit declaration of function 'csum_ipv6_magic'; did you mean 'csum_tcpudp_magic'? [-Werror=implicit-function-declaration]
78 | uh->check = csum_ipv6_magic(&ka->saddr.in6, &ka->daddr.in6,
| ^~~~~~~~~~~~~~~
| csum_tcpudp_magic
cc1: some warnings being treated as errors
vim +78 net/xfrm/xfrm_nat_keepalive.c
64
65 #if IS_ENABLED(CONFIG_IPV6)
66 static int nat_keepalive_send_ipv6(struct sk_buff *skb,
67 struct nat_keepalive *ka,
68 struct udphdr *uh)
69 {
70 struct net *net = ka->net;
71 struct dst_entry *dst;
72 struct flowi6 fl6;
73 struct sock *sk;
74 __wsum csum;
75 int err;
76
77 csum = skb_checksum(skb, 0, skb->len, 0);
> 78 uh->check = csum_ipv6_magic(&ka->saddr.in6, &ka->daddr.in6,
79 skb->len, IPPROTO_UDP, csum);
80 if (uh->check == 0)
81 uh->check = CSUM_MANGLED_0;
82
83 memset(&fl6, 0, sizeof(fl6));
84 fl6.flowi6_mark = skb->mark;
85 fl6.saddr = ka->saddr.in6;
86 fl6.daddr = ka->daddr.in6;
87 fl6.flowi6_proto = IPPROTO_UDP;
88 fl6.fl6_sport = ka->encap_sport;
89 fl6.fl6_dport = ka->encap_dport;
90
91 sk = *this_cpu_ptr(&nat_keepalive_sk_ipv6);
92 sock_net_set(sk, net);
93 dst = ipv6_stub->ipv6_dst_lookup_flow(net, sk, &fl6, NULL);
94 if (IS_ERR(dst))
95 return PTR_ERR(dst);
96
97 skb_dst_set(skb, dst);
98 err = ipv6_stub->ip6_xmit(sk, skb, &fl6, skb->mark, NULL, 0, 0);
99 sock_net_set(sk, &init_net);
100 return err;
101 }
102 #endif
103
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-12-14 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 18:01 [PATCH ipsec-next,v2] xfrm: support sending NAT keepalives in ESP in UDP states Eyal Birger
2023-12-10 18:47 ` [devel-ipsec] [PATCH ipsec-next, v2] " Michael Richardson
2023-12-10 19:14 ` Eyal Birger
2023-12-10 21:06 ` Michael Richardson
2023-12-14 18:51 ` kernel test robot [this message]
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=202312150227.iYQMDIJT-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=devel@linux-ipsec.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nharold@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=paul@nohats.ca \
--cc=steffen.klassert@secunet.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 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.