From: kernel test robot <lkp@intel.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Luis Chamberlain <mcgrof@kernel.org>,
Jessica Yu <jeyu@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>
Subject: Re: [PATCH bpf-next v5 1/9] kernel: Add kallsyms_on_each_symbol variant for single module
Date: Sat, 1 Jan 2022 18:03:45 +0800 [thread overview]
Message-ID: <202201011858.vOPCCeDV-lkp@intel.com> (raw)
In-Reply-To: <20211230023705.3860970-2-memxor@gmail.com>
Hi Kumar,
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/Kumar-Kartikeya-Dwivedi/Introduce-unstable-CT-lookup-helpers/20211230-103958
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: ia64-randconfig-s031-20211230 (https://download.01.org/0day-ci/archive/20220101/202201011858.vOPCCeDV-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/25d6b438335605e4e002f7afde50a3eaf17a0b6c
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Kumar-Kartikeya-Dwivedi/Introduce-unstable-CT-lookup-helpers/20211230-103958
git checkout 25d6b438335605e4e002f7afde50a3eaf17a0b6c
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=ia64 SHELL=/bin/bash
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/module.c:2762:23: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct mod_kallsyms [noderef] __rcu *kallsyms @@ got void * @@
kernel/module.c:2762:23: sparse: expected struct mod_kallsyms [noderef] __rcu *kallsyms
kernel/module.c:2762:23: sparse: got void *
>> kernel/module.c:4510:18: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct mod_kallsyms *kallsyms @@ got struct mod_kallsyms [noderef] __rcu *kallsyms @@
kernel/module.c:4510:18: sparse: expected struct mod_kallsyms *kallsyms
kernel/module.c:4510:18: sparse: got struct mod_kallsyms [noderef] __rcu *kallsyms
kernel/module.c:2764:12: sparse: sparse: dereference of noderef expression
kernel/module.c:2765:12: sparse: sparse: dereference of noderef expression
kernel/module.c:2767:12: sparse: sparse: dereference of noderef expression
kernel/module.c:2768:12: sparse: sparse: dereference of noderef expression
kernel/module.c:2777:18: sparse: sparse: dereference of noderef expression
kernel/module.c:2778:35: sparse: sparse: dereference of noderef expression
kernel/module.c:2779:20: sparse: sparse: dereference of noderef expression
kernel/module.c:2784:32: sparse: sparse: dereference of noderef expression
kernel/module.c:2787:45: sparse: sparse: dereference of noderef expression
vim +4510 kernel/module.c
4499
4500 int module_kallsyms_on_each_symbol(struct module *mod,
4501 int (*fn)(void *, const char *,
4502 struct module *, unsigned long),
4503 void *data)
4504 {
4505 struct mod_kallsyms *kallsyms;
4506 int ret = 0;
4507
4508 mutex_lock(&module_mutex);
4509 /* We hold module_mutex: no need for rcu_dereference_sched */
> 4510 kallsyms = mod->kallsyms;
4511 if (mod->state != MODULE_STATE_UNFORMED)
4512 ret = __module_kallsyms_on_each_symbol(kallsyms, mod, fn, data);
4513 mutex_unlock(&module_mutex);
4514
4515 return ret;
4516 }
4517
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-01-01 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 2:36 [PATCH bpf-next v5 0/9] Introduce unstable CT lookup helpers Kumar Kartikeya Dwivedi
2021-12-30 2:36 ` [PATCH bpf-next v5 1/9] kernel: Add kallsyms_on_each_symbol variant for single module Kumar Kartikeya Dwivedi
2022-01-01 10:03 ` kernel test robot [this message]
2021-12-30 2:36 ` [PATCH bpf-next v5 2/9] bpf: Prepare kfunc BTF ID sets when parsing kernel BTF Kumar Kartikeya Dwivedi
2021-12-31 2:23 ` Alexei Starovoitov
2021-12-31 3:45 ` Kumar Kartikeya Dwivedi
2021-12-31 16:56 ` Alexei Starovoitov
2021-12-30 2:36 ` [PATCH bpf-next v5 3/9] bpf: Remove check_kfunc_call callback and old kfunc BTF ID API Kumar Kartikeya Dwivedi
2021-12-30 2:37 ` [PATCH bpf-next v5 4/9] bpf: Introduce mem, size argument pair support for kfunc Kumar Kartikeya Dwivedi
2021-12-30 2:37 ` [PATCH bpf-next v5 5/9] bpf: Add reference tracking support to kfunc Kumar Kartikeya Dwivedi
2021-12-30 2:37 ` [PATCH bpf-next v5 6/9] net/netfilter: Add unstable CT lookup helpers for XDP and TC-BPF Kumar Kartikeya Dwivedi
2021-12-30 2:37 ` [PATCH bpf-next v5 7/9] selftests/bpf: Add test for unstable CT lookup API Kumar Kartikeya Dwivedi
2021-12-30 2:37 ` [PATCH bpf-next v5 8/9] selftests/bpf: Add test_verifier support to fixup kfunc call insns Kumar Kartikeya Dwivedi
2021-12-30 2:37 ` [PATCH bpf-next v5 9/9] selftests/bpf: Extend kfunc selftests Kumar Kartikeya Dwivedi
2021-12-30 3:04 ` [PATCH bpf-next v5 0/9] Introduce unstable CT lookup helpers Kumar Kartikeya Dwivedi
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=202201011858.vOPCCeDV-lkp@intel.com \
--to=lkp@intel.com \
--cc=bpf@vger.kernel.org \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pmladek@suse.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).