From: kbuild test robot <lkp@intel.com>
To: Andrii Nakryiko <andriin@fb.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
daniel@iogearbox.net
Cc: kbuild-all@lists.01.org, andrii.nakryiko@gmail.com,
kernel-team@fb.com, Andrii Nakryiko <andriin@fb.com>
Subject: Re: [PATCH v2 bpf-next 04/10] bpf: add support for BPF_OBJ_GET_INFO_BY_FD for bpf_link
Date: Wed, 29 Apr 2020 05:55:32 +0800 [thread overview]
Message-ID: <202004290506.bYgadzx3%lkp@intel.com> (raw)
In-Reply-To: <20200428054944.4015462-5-andriin@fb.com>
[-- Attachment #1: Type: text/plain, Size: 2894 bytes --]
Hi Andrii,
I love your patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
[also build test ERROR on bpf/master cgroup/for-next net/master net-next/master v5.7-rc3 next-20200428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Andrii-Nakryiko/bpf_link-observability-APIs/20200428-215720
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: sh-randconfig-a001-20200428 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
sh4-linux-ld: kernel/bpf/syscall.o: in function `bpf_raw_tp_link_fill_link_info':
>> kernel/bpf/syscall.c:2570: undefined reference to `__get_user_unknown'
vim +2570 kernel/bpf/syscall.c
2547
2548 static int bpf_raw_tp_link_fill_link_info(const struct bpf_link *link,
2549 struct bpf_link_info *info,
2550 const struct bpf_link_info *uinfo,
2551 u32 info_len)
2552 {
2553 struct bpf_raw_tp_link *raw_tp_link =
2554 container_of(link, struct bpf_raw_tp_link, link);
2555 u64 ubuf_ptr;
2556 char __user *ubuf = u64_to_user_ptr(uinfo->raw_tracepoint.tp_name);
2557 const char *tp_name = raw_tp_link->btp->tp->name;
2558 size_t tp_len;
2559 u32 ulen;
2560
2561 if (get_user(ulen, &uinfo->raw_tracepoint.tp_name_len))
2562 return -EFAULT;
2563 if (get_user(ubuf_ptr, &uinfo->raw_tracepoint.tp_name))
2564 return -EFAULT;
2565 ubuf = u64_to_user_ptr(ubuf_ptr);
2566
2567 if (ulen && !ubuf)
2568 return -EINVAL;
2569 if (!ubuf)
> 2570 return 0;
2571
2572 tp_len = strlen(raw_tp_link->btp->tp->name);
2573 info->raw_tracepoint.tp_name_len = tp_len + 1;
2574 info->raw_tracepoint.tp_name = (u64)(unsigned long)ubuf;
2575
2576 if (ulen >= tp_len + 1) {
2577 if (copy_to_user(ubuf, tp_name, tp_len + 1))
2578 return -EFAULT;
2579 } else {
2580 char zero = '\0';
2581
2582 if (copy_to_user(ubuf, tp_name, ulen - 1))
2583 return -EFAULT;
2584 if (put_user(zero, ubuf + ulen - 1))
2585 return -EFAULT;
2586 return -ENOSPC;
2587 }
2588
2589 return 0;
2590 }
2591
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25376 bytes --]
next prev parent reply other threads:[~2020-04-28 21:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 5:49 [PATCH v2 bpf-next 00/10] bpf_link observability APIs Andrii Nakryiko
2020-04-28 5:49 ` [PATCH v2 bpf-next 01/10] bpf: refactor bpf_link update handling Andrii Nakryiko
2020-04-28 5:49 ` [PATCH v2 bpf-next 02/10] bpf: allocate ID for bpf_link Andrii Nakryiko
2020-04-28 17:31 ` Alexei Starovoitov
2020-04-28 18:56 ` Andrii Nakryiko
2020-04-28 20:38 ` Alexei Starovoitov
2020-04-28 22:33 ` Andrii Nakryiko
2020-04-28 22:43 ` Alexei Starovoitov
2020-04-28 23:25 ` Andrii Nakryiko
2020-04-29 0:11 ` Alexei Starovoitov
2020-04-28 5:49 ` [PATCH v2 bpf-next 03/10] bpf: support GET_FD_BY_ID and GET_NEXT_ID " Andrii Nakryiko
2020-04-28 5:49 ` [PATCH v2 bpf-next 04/10] bpf: add support for BPF_OBJ_GET_INFO_BY_FD " Andrii Nakryiko
2020-04-28 9:46 ` Toke Høiland-Jørgensen
2020-04-28 16:27 ` Andrii Nakryiko
2020-04-28 18:31 ` Toke Høiland-Jørgensen
2020-04-28 21:55 ` kbuild test robot [this message]
2020-04-28 5:49 ` [PATCH v2 bpf-next 05/10] libbpf: add low-level APIs for new bpf_link commands Andrii Nakryiko
2020-04-28 5:49 ` [PATCH v2 bpf-next 06/10] selftests/bpf: test bpf_link's get_next_id, get_fd_by_id, and get_obj_info Andrii Nakryiko
2020-04-28 5:49 ` [PATCH v2 bpf-next 07/10] bpftool: expose attach_type-to-string array to non-cgroup code Andrii Nakryiko
2020-04-28 8:22 ` Quentin Monnet
2020-04-28 5:49 ` [PATCH v2 bpf-next 08/10] bpftool: add bpf_link show and pin support Andrii Nakryiko
2020-04-28 8:23 ` Quentin Monnet
2020-04-28 5:49 ` [PATCH v2 bpf-next 09/10] bpftool: add bpftool-link manpage Andrii Nakryiko
2020-04-28 8:23 ` Quentin Monnet
2020-04-28 5:49 ` [PATCH v2 bpf-next 10/10] bpftool: add link bash completions Andrii Nakryiko
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=202004290506.bYgadzx3%lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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