From: kernel test robot <lkp@intel.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Eric Dumazet <edumazet@google.com>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next 3/3] dst_cache: let rt_uncached cope with dst_cache cleanup
Date: Fri, 31 May 2024 18:53:48 +0800 [thread overview]
Message-ID: <202405311808.vqBTwxEf-lkp@intel.com> (raw)
In-Reply-To: <cd710487a34149654a5ff73a8c0df9b1d3fc73a9.1717087015.git.pabeni@redhat.com>
Hi Paolo,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Paolo-Abeni/ipv6-use-a-new-flag-to-indicate-elevated-refcount/20240531-012716
base: net-next/main
patch link: https://lore.kernel.org/r/cd710487a34149654a5ff73a8c0df9b1d3fc73a9.1717087015.git.pabeni%40redhat.com
patch subject: [PATCH net-next 3/3] dst_cache: let rt_uncached cope with dst_cache cleanup
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20240531/202405311808.vqBTwxEf-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240531/202405311808.vqBTwxEf-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/202405311808.vqBTwxEf-lkp@intel.com/
All errors (new ones prefixed by >>):
aarch64-linux-ld: Unexpected GOT/PLT entries detected!
aarch64-linux-ld: Unexpected run-time procedure linkages detected!
aarch64-linux-ld: net/core/dst_cache.o: in function `dst_cache_set_ip6':
>> net/core/dst_cache.c:123:(.text+0x240): undefined reference to `rt6_uncached_list_add'
vim +123 net/core/dst_cache.c
109
110 #if IS_ENABLED(CONFIG_IPV6)
111 void dst_cache_set_ip6(struct dst_cache *dst_cache, struct dst_entry *dst,
112 const struct in6_addr *saddr)
113 {
114 struct dst_cache_pcpu *idst;
115
116 if (!dst_cache->cache)
117 return;
118
119 idst = this_cpu_ptr(dst_cache->cache);
120 dst_cache_per_cpu_dst_set(idst, dst,
121 rt6_get_cookie(dst_rt6_info(dst)));
122 if (dst && list_empty(&dst->rt_uncached))
> 123 rt6_uncached_list_add(dst_rt6_info(dst));
124
125 idst->in6_saddr = *saddr;
126 }
127 EXPORT_SYMBOL_GPL(dst_cache_set_ip6);
128
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-31 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 17:18 [PATCH net-next 0/3] dst_cache: cope with device removal Paolo Abeni
2024-05-30 17:21 ` Paolo Abeni
2024-05-30 17:21 ` [PATCH net-next 1/3] ipv6: use a new flag to indicate elevated refcount Paolo Abeni
2024-05-30 17:21 ` [PATCH net-next 2/3] ipv4: obsolete routes moved out of per cpu cache Paolo Abeni
2024-05-30 17:21 ` [PATCH net-next 3/3] dst_cache: let rt_uncached cope with dst_cache cleanup Paolo Abeni
2024-05-30 17:46 ` Eric Dumazet
2024-05-31 10:53 ` kernel test robot [this message]
2024-05-31 17:32 ` kernel test robot
2024-05-30 17:38 ` [PATCH net-next 0/3] dst_cache: cope with device removal Eric Dumazet
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=202405311808.vqBTwxEf-lkp@intel.com \
--to=lkp@intel.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).