From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v5 bpf-next 2/6] bpf: move to generic BTF show support, apply it to seq files/strings
Date: Sat, 19 Sep 2020 02:32:55 +0800 [thread overview]
Message-ID: <202009190213.Qw9IIZxu%lkp@intel.com> (raw)
In-Reply-To: <1600436075-2961-3-git-send-email-alan.maguire@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
Hi Alan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Alan-Maguire/bpf-add-helpers-to-support-BTF-based-kernel-data-display/20200918-213932
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: x86_64-randconfig-s021-20200917 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-201-g24bdaac6-dirty
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/bpf/btf.c:2465:17: sparse: sparse: Using plain integer as NULL pointer
kernel/bpf/btf.c:2467:17: sparse: sparse: Using plain integer as NULL pointer
kernel/bpf/btf.c:3244:17: sparse: sparse: Using plain integer as NULL pointer
kernel/bpf/btf.c:3585:9: sparse: sparse: Using plain integer as NULL pointer
>> kernel/bpf/btf.c:5310:6: sparse: sparse: symbol 'btf_type_show' was not declared. Should it be static?
Please review and possibly fold the followup patch.
# https://github.com/0day-ci/linux/commit/a85186d405b24251bfd7179ae1949f3458e9702d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Alan-Maguire/bpf-add-helpers-to-support-BTF-based-kernel-data-display/20200918-213932
git checkout a85186d405b24251bfd7179ae1949f3458e9702d
vim +2465 kernel/bpf/btf.c
2452
2453 static void btf_ptr_show(const struct btf *btf, const struct btf_type *t,
2454 u32 type_id, void *data, u8 bits_offset,
2455 struct btf_show *show)
2456 {
2457 void *safe_data;
2458
2459 safe_data = btf_show_start_type(show, t, type_id, data);
2460 if (!safe_data)
2461 return;
2462
2463 /* It is a hashed value unless BTF_SHOW_PTR_RAW is specified */
2464 if (show->flags & BTF_SHOW_PTR_RAW)
> 2465 btf_show_type_value(show, "0x%px", *(void **)safe_data);
2466 else
2467 btf_show_type_value(show, "0x%p", *(void **)safe_data);
2468 btf_show_end_type(show);
2469 }
2470
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30065 bytes --]
next prev parent reply other threads:[~2020-09-18 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 13:34 [PATCH v5 bpf-next 0/6] bpf: add helpers to support BTF-based kernel data display Alan Maguire
2020-09-18 13:34 ` [PATCH v5 bpf-next 1/6] bpf: provide function to get vmlinux BTF information Alan Maguire
2020-09-18 13:34 ` [PATCH v5 bpf-next 2/6] bpf: move to generic BTF show support, apply it to seq files/strings Alan Maguire
2020-09-18 18:20 ` kernel test robot
2020-09-18 18:32 ` kernel test robot [this message]
2020-09-18 18:32 ` [RFC PATCH] bpf: btf_type_show() can be static kernel test robot
2020-09-18 18:44 ` [PATCH v5 bpf-next 2/6] bpf: move to generic BTF show support, apply it to seq files/strings kernel test robot
2020-09-18 13:34 ` [PATCH v5 bpf-next 3/6] bpf: add bpf_btf_snprintf helper Alan Maguire
2020-09-18 23:53 ` kernel test robot
2020-09-19 0:20 ` kernel test robot
2020-09-18 13:34 ` [PATCH v5 bpf-next 4/6] selftests/bpf: add bpf_btf_snprintf helper tests Alan Maguire
2020-09-18 13:34 ` [PATCH v5 bpf-next 5/6] bpf: add bpf_seq_btf_write helper Alan Maguire
2020-09-22 1:10 ` Alexei Starovoitov
2020-09-18 13:34 ` [PATCH v5 bpf-next 6/6] selftests/bpf: add test for " Alan Maguire
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=202009190213.Qw9IIZxu%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.