From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 09/12] module: Move kallsyms support into a separate file
Date: Thu, 30 Dec 2021 11:19:29 +0800 [thread overview]
Message-ID: <202112301104.CFQGCV4b-lkp@intel.com> (raw)
In-Reply-To: <20211228213041.1356334-10-atomlin@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3878 bytes --]
Hi Aaron,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on jeyu/modules-next]
[also build test WARNING on v5.16-rc7 next-20211224]
[cannot apply to linus/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]
url: https://github.com/0day-ci/linux/commits/Aaron-Tomlin/module-Move-all-into-module/20211229-063051
base: https://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git modules-next
config: x86_64-rhel-8.3-kselftests (https://download.01.org/0day-ci/archive/20211230/202112301104.CFQGCV4b-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/dca0a654ac33ddd67bc916d2b906e610d94d9dfc
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Aaron-Tomlin/module-Move-all-into-module/20211229-063051
git checkout dca0a654ac33ddd67bc916d2b906e610d94d9dfc
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 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/kallsyms.c: note: in included file:
include/linux/module.h:380:3: sparse: sparse: symbol 'mod_tree' was not declared. Should it be static?
kernel/module/kallsyms.c:178:23: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct mod_kallsyms [noderef] __rcu *kallsyms @@ got void * @@
kernel/module/kallsyms.c:178:23: sparse: expected struct mod_kallsyms [noderef] __rcu *kallsyms
kernel/module/kallsyms.c:178:23: sparse: got void *
>> kernel/module/kallsyms.c:486:52: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct mod_kallsyms *kallsyms @@ got struct mod_kallsyms [noderef] __rcu *kallsyms @@
kernel/module/kallsyms.c:486:52: sparse: expected struct mod_kallsyms *kallsyms
kernel/module/kallsyms.c:486:52: sparse: got struct mod_kallsyms [noderef] __rcu *kallsyms
kernel/module/kallsyms.c:180:12: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:181:12: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:183:12: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:184:12: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:193:18: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:194:35: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:195:20: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:200:32: sparse: sparse: dereference of noderef expression
kernel/module/kallsyms.c:203:45: sparse: sparse: dereference of noderef expression
vim +486 kernel/module/kallsyms.c
473
474 #ifdef CONFIG_LIVEPATCH
475 int module_kallsyms_on_each_symbol(int (*fn)(void *, const char *,
476 struct module *, unsigned long),
477 void *data)
478 {
479 struct module *mod;
480 unsigned int i;
481 int ret = 0;
482
483 mutex_lock(&module_mutex);
484 list_for_each_entry(mod, &modules, list) {
485 /* We hold module_mutex: no need for rcu_dereference_sched */
> 486 struct mod_kallsyms *kallsyms = mod->kallsyms;
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2021-12-30 3:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 17:33 [RFC PATCH] module: Introduce module unload taint tracking Aaron Tomlin
2021-11-24 22:52 ` kernel test robot
2021-11-24 22:52 ` kernel test robot
2021-11-25 6:55 ` kernel test robot
2021-12-08 20:47 ` Luis Chamberlain
2021-12-09 16:49 ` Aaron Tomlin
2021-12-09 23:42 ` Luis Chamberlain
2021-12-10 10:00 ` Petr Mladek
2021-12-10 16:09 ` Aaron Tomlin
2021-12-10 17:09 ` Luis Chamberlain
2021-12-13 15:16 ` Petr Mladek
2021-12-21 11:58 ` Aaron Tomlin
2021-12-10 17:03 ` Luis Chamberlain
2021-12-10 15:48 ` Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 00/12] module: core code clean up Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 01/12] module: Move all into module/ Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 02/12] module: Simple refactor in preparation for split Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 03/12] module: Move livepatch support to a separate file Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 04/12] module: Move latched RB-tree " Aaron Tomlin
2021-12-29 0:10 ` kernel test robot
2021-12-29 0:40 ` kernel test robot
2021-12-28 21:30 ` [RFC PATCH 05/12] module: Move arch strict rwx " Aaron Tomlin
2022-01-12 16:13 ` Luis Chamberlain
2021-12-28 21:30 ` [RFC PATCH 06/12] module: Move " Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 07/12] module: Move extra signature support out of core code Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 08/12] module: Move kmemleak support to a separate file Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 09/12] module: Move kallsyms support into " Aaron Tomlin
2021-12-29 0:30 ` kernel test robot
2021-12-29 3:53 ` kernel test robot
2021-12-30 3:19 ` kernel test robot [this message]
2021-12-28 21:30 ` [RFC PATCH 10/12] module: Move procfs " Aaron Tomlin
2021-12-28 21:30 ` [RFC PATCH 11/12] module: Move sysfs " Aaron Tomlin
2022-01-12 16:20 ` Luis Chamberlain
2021-12-28 21:30 ` [RFC PATCH 12/12] module: Move kdb_modules list out of core code Aaron Tomlin
2021-12-29 8:58 ` [RFC PATCH 00/12] module: core code clean up Aaron Tomlin
2022-01-12 16:21 ` Luis Chamberlain
2021-12-13 13:00 ` [RFC PATCH] module: Introduce module unload taint tracking Allen
2021-12-20 19:23 ` Luis Chamberlain
2021-12-21 11:44 ` Aaron Tomlin
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=202112301104.CFQGCV4b-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.