From: kernel test robot <lkp@intel.com>
To: shiming cheng <shiming.cheng@mediatek.com>,
willemdebruijn.kernel@gmail.com, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
netdev@vger.kernel.org, lena.wang@mediatek.com,
shiming cheng <shiming.cheng@mediatek.com>
Subject: Re: [PATCH] ipv6: socket SO_BINDTODEVICE lookup routing fail without IPv6 rule.
Date: Thu, 2 Jan 2025 21:03:37 +0800 [thread overview]
Message-ID: <202501022057.YOhf05jy-lkp@intel.com> (raw)
In-Reply-To: <20250102095114.25860-1-shiming.cheng@mediatek.com>
Hi shiming,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
[also build test ERROR on net/main soc/for-next linus/master v6.13-rc5 next-20241220]
[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/shiming-cheng/ipv6-socket-SO_BINDTODEVICE-lookup-routing-fail-without-IPv6-rule/20250102-174939
base: net-next/main
patch link: https://lore.kernel.org/r/20250102095114.25860-1-shiming.cheng%40mediatek.com
patch subject: [PATCH] ipv6: socket SO_BINDTODEVICE lookup routing fail without IPv6 rule.
config: riscv-randconfig-001-20250102 (https://download.01.org/0day-ci/archive/20250102/202501022057.YOhf05jy-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250102/202501022057.YOhf05jy-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/202501022057.YOhf05jy-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/ipv6/ip6_output.c:1239:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1259:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1294:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1311:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1317:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1327:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1348:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1429:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1834:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1867:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1876:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1898:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1978:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:1998:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:2013:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:2027:1: error: function definition is not allowed here
{
^
net/ipv6/ip6_output.c:2039:1: error: function definition is not allowed here
{
^
>> net/ipv6/ip6_output.c:2074:2: error: expected '}'
}
^
net/ipv6/ip6_output.c:1107:1: note: to match this '{'
{
^
18 errors generated.
vim +1239 net/ipv6/ip6_output.c
34a0b3cdc07874 Adrian Bunk 2005-11-29 1225
497c615abad7ee Herbert Xu 2006-07-30 1226 /**
497c615abad7ee Herbert Xu 2006-07-30 1227 * ip6_dst_lookup - perform route lookup on flow
b51cd7c834dba0 Andrew Lunn 2020-07-13 1228 * @net: Network namespace to perform lookup in
497c615abad7ee Herbert Xu 2006-07-30 1229 * @sk: socket which provides route info
497c615abad7ee Herbert Xu 2006-07-30 1230 * @dst: pointer to dst_entry * for result
4c9483b2fb5d25 David S. Miller 2011-03-12 1231 * @fl6: flow to lookup
497c615abad7ee Herbert Xu 2006-07-30 1232 *
497c615abad7ee Herbert Xu 2006-07-30 1233 * This function performs a route lookup on the given flow.
497c615abad7ee Herbert Xu 2006-07-30 1234 *
497c615abad7ee Herbert Xu 2006-07-30 1235 * It returns zero on success, or a standard errno code on error.
497c615abad7ee Herbert Xu 2006-07-30 1236 */
343d60aada5a35 Roopa Prabhu 2015-07-30 1237 int ip6_dst_lookup(struct net *net, struct sock *sk, struct dst_entry **dst,
343d60aada5a35 Roopa Prabhu 2015-07-30 1238 struct flowi6 *fl6)
497c615abad7ee Herbert Xu 2006-07-30 @1239 {
497c615abad7ee Herbert Xu 2006-07-30 1240 *dst = NULL;
343d60aada5a35 Roopa Prabhu 2015-07-30 1241 return ip6_dst_lookup_tail(net, sk, dst, fl6);
497c615abad7ee Herbert Xu 2006-07-30 1242 }
3cf3dc6c2e05e6 Arnaldo Carvalho de Melo 2005-12-13 1243 EXPORT_SYMBOL_GPL(ip6_dst_lookup);
3cf3dc6c2e05e6 Arnaldo Carvalho de Melo 2005-12-13 1244
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-02 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 9:51 [PATCH] ipv6: socket SO_BINDTODEVICE lookup routing fail without IPv6 rule shiming cheng
2025-01-02 12:12 ` kernel test robot
2025-01-02 13:03 ` kernel test robot [this message]
2025-01-02 13:48 ` kernel test robot
2025-01-02 15:57 ` David Ahern
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=202501022057.YOhf05jy-lkp@intel.com \
--to=lkp@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lena.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=shiming.cheng@mediatek.com \
--cc=willemdebruijn.kernel@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