From: kernel test robot <lkp@intel.com>
To: Gustavo Luiz Duarte <gustavold@gmail.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>,
Breno Leitao <leitao@debian.org>,
Willem de Bruijn <willemb@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ipmr: Call ipmr_ioctl() directly from ipmr_sk_ioctl()
Date: Wed, 9 Aug 2023 11:26:19 +0800 [thread overview]
Message-ID: <202308091122.z4eVvCI5-lkp@intel.com> (raw)
In-Reply-To: <20230731145713.178509-1-gustavold@gmail.com>
Hi Gustavo,
kernel test robot noticed the following build errors:
[auto build test ERROR on net/main]
[also build test ERROR on net-next/main linus/master v6.5-rc5 next-20230808]
[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/Gustavo-Luiz-Duarte/net-ipmr-Call-ipmr_ioctl-directly-from-ipmr_sk_ioctl/20230731-225918
base: net/main
patch link: https://lore.kernel.org/r/20230731145713.178509-1-gustavold%40gmail.com
patch subject: [PATCH] net: ipmr: Call ipmr_ioctl() directly from ipmr_sk_ioctl()
config: x86_64-randconfig-x054-20230808 (https://download.01.org/0day-ci/archive/20230809/202308091122.z4eVvCI5-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230809/202308091122.z4eVvCI5-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/202308091122.z4eVvCI5-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: net/core/sock.o: in function `ip6mr_sk_ioctl':
>> include/linux/mroute6.h:115: undefined reference to `ip6mr_ioctl'
>> ld: include/linux/mroute6.h:130: undefined reference to `ip6mr_ioctl'
vim +115 include/linux/mroute6.h
95
96 struct rtmsg;
97 extern int ip6mr_get_route(struct net *net, struct sk_buff *skb,
98 struct rtmsg *rtm, u32 portid);
99
100 #ifdef CONFIG_IPV6_MROUTE
101 bool mroute6_is_socket(struct net *net, struct sk_buff *skb);
102 extern int ip6mr_sk_done(struct sock *sk);
103 static inline int ip6mr_sk_ioctl(struct sock *sk, unsigned int cmd,
104 void __user *arg)
105 {
106 int ret;
107
108 switch (cmd) {
109 case SIOCGETMIFCNT_IN6: {
110 struct sioc_mif_req6 karg;
111
112 if (copy_from_user(&karg, arg, sizeof(karg)))
113 return -EFAULT;
114
> 115 ret = ip6mr_ioctl(sk, cmd, &karg);
116 if (ret)
117 return ret;
118
119 if (copy_to_user(arg, &karg, sizeof(karg)))
120 return -EFAULT;
121
122 return 0;
123 }
124 case SIOCGETSGCNT_IN6: {
125 struct sioc_sg_req6 karg;
126
127 if (copy_from_user(&karg, arg, sizeof(karg)))
128 return -EFAULT;
129
> 130 ret = ip6mr_ioctl(sk, cmd, &karg);
131 if (ret)
132 return ret;
133
134 if (copy_to_user(arg, &karg, sizeof(karg)))
135 return -EFAULT;
136
137 return 0;
138 }
139 }
140
141 return 1;
142 }
143 #else
144 static inline bool mroute6_is_socket(struct net *net, struct sk_buff *skb)
145 {
146 return false;
147 }
148 static inline int ip6mr_sk_done(struct sock *sk)
149 {
150 return 0;
151 }
152
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-09 3:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 14:57 [PATCH] net: ipmr: Call ipmr_ioctl() directly from ipmr_sk_ioctl() Gustavo Luiz Duarte
2023-07-31 18:27 ` Willem de Bruijn
2023-08-09 3:26 ` kernel test robot [this message]
2023-08-09 22:25 ` kernel test robot
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=202308091122.z4eVvCI5-lkp@intel.com \
--to=lkp@intel.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gustavold@gmail.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=willemb@google.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