From: kernel test robot <lkp@intel.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
Alexander Lobakin <aleksander.lobakin@intel.com>
Subject: [net-next:master 1/30] net/xdp/xsk.c:1322:16: error: implicit declaration of function 'remap_vmalloc_range'; did you mean 'ida_alloc_range'?
Date: Tue, 21 Feb 2023 00:19:10 +0800 [thread overview]
Message-ID: <202302210041.kpPQLlNQ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 3fcdf2dfefb6313ea0395519d1784808c0b6559b
commit: 9f78bf330a66cd400b3e00f370f597e9fa939207 [1/30] xsk: support use vaddr as ring
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20230221/202302210041.kpPQLlNQ-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=9f78bf330a66cd400b3e00f370f597e9fa939207
git remote add net-next https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
git fetch --no-tags net-next master
git checkout 9f78bf330a66cd400b3e00f370f597e9fa939207
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh SHELL=/bin/bash net/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302210041.kpPQLlNQ-lkp@intel.com/
All errors (new ones prefixed by >>):
net/xdp/xsk.c: In function 'xsk_mmap':
>> net/xdp/xsk.c:1322:16: error: implicit declaration of function 'remap_vmalloc_range'; did you mean 'ida_alloc_range'? [-Werror=implicit-function-declaration]
1322 | return remap_vmalloc_range(vma, q->ring, 0);
| ^~~~~~~~~~~~~~~~~~~
| ida_alloc_range
cc1: some warnings being treated as errors
vim +1322 net/xdp/xsk.c
1289
1290 static int xsk_mmap(struct file *file, struct socket *sock,
1291 struct vm_area_struct *vma)
1292 {
1293 loff_t offset = (loff_t)vma->vm_pgoff << PAGE_SHIFT;
1294 unsigned long size = vma->vm_end - vma->vm_start;
1295 struct xdp_sock *xs = xdp_sk(sock->sk);
1296 struct xsk_queue *q = NULL;
1297
1298 if (READ_ONCE(xs->state) != XSK_READY)
1299 return -EBUSY;
1300
1301 if (offset == XDP_PGOFF_RX_RING) {
1302 q = READ_ONCE(xs->rx);
1303 } else if (offset == XDP_PGOFF_TX_RING) {
1304 q = READ_ONCE(xs->tx);
1305 } else {
1306 /* Matches the smp_wmb() in XDP_UMEM_REG */
1307 smp_rmb();
1308 if (offset == XDP_UMEM_PGOFF_FILL_RING)
1309 q = READ_ONCE(xs->fq_tmp);
1310 else if (offset == XDP_UMEM_PGOFF_COMPLETION_RING)
1311 q = READ_ONCE(xs->cq_tmp);
1312 }
1313
1314 if (!q)
1315 return -EINVAL;
1316
1317 /* Matches the smp_wmb() in xsk_init_queue */
1318 smp_rmb();
1319 if (size > q->ring_vmalloc_size)
1320 return -EINVAL;
1321
> 1322 return remap_vmalloc_range(vma, q->ring, 0);
1323 }
1324
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-20 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202302210041.kpPQLlNQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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).