From: kernel test robot <lkp@intel.com>
To: Jun Yao <yaojun8558363@gmail.com>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, dsahern@kernel.org,
idosch@nvidia.com, Jun Yao <yaojun8558363@gmail.com>
Subject: Re: [PATCH] xfrm: avoid stale tunnel pointers in deferred input callbacks
Date: Thu, 12 Nov 2026 06:10:37 +0800 [thread overview]
Message-ID: <202611120624.jcKHEACy-lkp@intel.com> (raw)
In-Reply-To: <20261111094629.230568-1-yaojun8558363@gmail.com>
Hi Jun,
kernel test robot noticed the following build errors:
[auto build test ERROR on klassert-ipsec-next/master]
[also build test ERROR on klassert-ipsec/master net/main net-next/main linus/master v7.4-rc2 next-20261110]
[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/Jun-Yao/xfrm-avoid-stale-tunnel-pointers-in-deferred-input-callbacks/20261111-174629
base: https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
patch link: https://lore.kernel.org/r/20261111094629.230568-1-yaojun8558363%40gmail.com
patch subject: [PATCH] xfrm: avoid stale tunnel pointers in deferred input callbacks
config: mips-xway_defconfig (https://download.01.org/0day-ci/archive/20261112/202611120624.jcKHEACy-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261112/202611120624.jcKHEACy-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/202611120624.jcKHEACy-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from net/core/sock.c:134:
include/net/xfrm.h:777:9: error: call to undeclared function 'skb_ext_add'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
777 | return skb_ext_add(skb, SKB_EXT_XFRM_TUNNEL);
| ^
include/net/xfrm.h:777:26: error: use of undeclared identifier 'SKB_EXT_XFRM_TUNNEL'; did you mean 'SKB_GSO_UDP_TUNNEL'?
777 | return skb_ext_add(skb, SKB_EXT_XFRM_TUNNEL);
| ^~~~~~~~~~~~~~~~~~~
| SKB_GSO_UDP_TUNNEL
include/linux/skbuff.h:697:2: note: 'SKB_GSO_UDP_TUNNEL' declared here
697 | SKB_GSO_UDP_TUNNEL = 1 << 10,
| ^
In file included from net/core/sock.c:134:
>> include/net/xfrm.h:777:9: error: incompatible integer to pointer conversion returning 'int' from a function with result type 'struct xfrm_tunnel_info *' [-Wint-conversion]
777 | return skb_ext_add(skb, SKB_EXT_XFRM_TUNNEL);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/net/xfrm.h:783:9: error: call to undeclared function 'skb_ext_find'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
783 | return skb_ext_find(skb, SKB_EXT_XFRM_TUNNEL);
| ^
include/net/xfrm.h:783:27: error: use of undeclared identifier 'SKB_EXT_XFRM_TUNNEL'; did you mean 'SKB_GSO_UDP_TUNNEL'?
783 | return skb_ext_find(skb, SKB_EXT_XFRM_TUNNEL);
| ^~~~~~~~~~~~~~~~~~~
| SKB_GSO_UDP_TUNNEL
include/linux/skbuff.h:697:2: note: 'SKB_GSO_UDP_TUNNEL' declared here
697 | SKB_GSO_UDP_TUNNEL = 1 << 10,
| ^
In file included from net/core/sock.c:134:
>> include/net/xfrm.h:783:9: error: incompatible integer to pointer conversion returning 'int' from a function with result type 'const struct xfrm_tunnel_info *' [-Wint-conversion]
783 | return skb_ext_find(skb, SKB_EXT_XFRM_TUNNEL);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/net/xfrm.h:788:19: error: use of undeclared identifier 'SKB_EXT_XFRM_TUNNEL'; did you mean 'SKB_GSO_UDP_TUNNEL'?
788 | skb_ext_del(skb, SKB_EXT_XFRM_TUNNEL);
| ^~~~~~~~~~~~~~~~~~~
| SKB_GSO_UDP_TUNNEL
include/linux/skbuff.h:697:2: note: 'SKB_GSO_UDP_TUNNEL' declared here
697 | SKB_GSO_UDP_TUNNEL = 1 << 10,
| ^
7 errors generated.
vim +777 include/net/xfrm.h
773
774 static inline struct xfrm_tunnel_info *
775 xfrm_tunnel_info_add(struct sk_buff *skb)
776 {
> 777 return skb_ext_add(skb, SKB_EXT_XFRM_TUNNEL);
778 }
779
780 static inline const struct xfrm_tunnel_info *
781 xfrm_tunnel_info(const struct sk_buff *skb)
782 {
> 783 return skb_ext_find(skb, SKB_EXT_XFRM_TUNNEL);
784 }
785
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-11-11 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 9:46 Jun Yao
2026-11-11 9:52 ` netdev-bot+sinfo
2026-11-11 14:01 ` Victor Nogueira
2026-11-11 21:26 ` kernel test robot
2026-11-11 22:10 ` 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=202611120624.jcKHEACy-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=yaojun8558363@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®