From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [paulmck-rcu:dev.2023.10.11a 7/28] kernel/locking/locktorture.c:127:23: sparse: sparse: symbol 'call_rcu_chain_list' was not declared. Should it be static?
Date: Thu, 30 Nov 2023 22:58:25 +0800 [thread overview]
Message-ID: <202311302248.667zLxFb-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "commit 5fabbc8a9e4cdf1b4d747c24f8fb87917f8bcc0f was found in branch paulmck-rcu/dev.2023.10.11a, not in new branch paulmck-rcu/dev.2023.11.03a"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: "Paul E. McKenney" <paulmck@kernel.org>
Hi Paul,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2023.10.11a
head: e8cc1332908682b309968c50157c6b272a0cafae
commit: 5fabbc8a9e4cdf1b4d747c24f8fb87917f8bcc0f [7/28] locktorture: Increase Hamming distance between call_rcu_chain and rcu_call_chains
:::::: branch date: 3 weeks ago
:::::: commit date: 7 weeks ago
config: i386-randconfig-063-20231013 (https://download.01.org/0day-ci/archive/20231130/202311302248.667zLxFb-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231130/202311302248.667zLxFb-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202311302248.667zLxFb-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/locking/locktorture.c:127:23: sparse: sparse: symbol 'call_rcu_chain_list' was not declared. Should it be static?
kernel/locking/locktorture.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/umh.h, include/linux/kmod.h, ...):
include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false
kernel/locking/locktorture.c:496:12: sparse: sparse: context imbalance in 'torture_mutex_lock' - wrong count at exit
kernel/locking/locktorture.c:512:13: sparse: sparse: context imbalance in 'torture_mutex_unlock' - wrong count at exit
kernel/locking/locktorture.c:570:12: sparse: sparse: context imbalance in 'torture_ww_mutex_lock' - wrong count at exit
kernel/locking/locktorture.c: note: in included file:
include/linux/ww_mutex.h:191:9: sparse: sparse: context imbalance in 'torture_ww_mutex_unlock' - wrong count at exit
kernel/locking/locktorture.c:665:12: sparse: sparse: context imbalance in 'torture_rtmutex_lock' - wrong count at exit
kernel/locking/locktorture.c:689:13: sparse: sparse: context imbalance in 'torture_rtmutex_unlock' - wrong count at exit
kernel/locking/locktorture.c:729:12: sparse: sparse: context imbalance in 'torture_rwsem_down_write' - wrong count at exit
kernel/locking/locktorture.c:745:13: sparse: sparse: context imbalance in 'torture_rwsem_up_write' - wrong count at exit
kernel/locking/locktorture.c:751:12: sparse: sparse: context imbalance in 'torture_rwsem_down_read' - wrong count at exit
kernel/locking/locktorture.c:769:13: sparse: sparse: context imbalance in 'torture_rwsem_up_read' - wrong count at exit
kernel/locking/locktorture.c:799:12: sparse: sparse: context imbalance in 'torture_percpu_rwsem_down_write' - wrong count at exit
kernel/locking/locktorture.c:806:13: sparse: sparse: context imbalance in 'torture_percpu_rwsem_up_write' - wrong count at exit
kernel/locking/locktorture.c: note: in included file:
include/linux/percpu-rwsem.h:70:9: sparse: sparse: context imbalance in 'torture_percpu_rwsem_down_read' - wrong count at exit
include/linux/percpu-rwsem.h:121:9: sparse: sparse: context imbalance in 'torture_percpu_rwsem_up_read' - wrong count at exit
vim +/call_rcu_chain_list +127 kernel/locking/locktorture.c
0af3fe1efa534a4 Paul E. McKenney 2014-02-04 122
7f993623e9ebcd6 Paul E. McKenney 2023-08-21 123 struct call_rcu_chain {
7f993623e9ebcd6 Paul E. McKenney 2023-08-21 124 struct rcu_head crc_rh;
7f993623e9ebcd6 Paul E. McKenney 2023-08-21 125 bool crc_stop;
7f993623e9ebcd6 Paul E. McKenney 2023-08-21 126 };
5fabbc8a9e4cdf1 Paul E. McKenney 2023-10-10 @127 struct call_rcu_chain *call_rcu_chain_list;
7f993623e9ebcd6 Paul E. McKenney 2023-08-21 128
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-30 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 14:58 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 18:48 [paulmck-rcu:dev.2023.10.11a 7/28] kernel/locking/locktorture.c:127:23: sparse: sparse: symbol 'call_rcu_chain_list' was not declared. Should it be static? kernel test robot
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=202311302248.667zLxFb-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.