From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>
Subject: [brauner-github:namespace-6.19 13/73] kernel/nstree.c:7:28: sparse: sparse: symbol 'ns_tree_lock' was not declared. Should it be static?
Date: Fri, 31 Oct 2025 14:00:57 +0800 [thread overview]
Message-ID: <202510311331.IAWNYwBY-lkp@intel.com> (raw)
tree: https://github.com/brauner/linux.git namespace-6.19
head: 232affb34bfb5be4df33a3e7bc92154e38f74535
commit: 6696d17cfe2b00c43717aecab6f461e1a68c7b28 [13/73] nstree: introduce a unified tree
config: nios2-randconfig-r113-20251031 (https://download.01.org/0day-ci/archive/20251031/202510311331.IAWNYwBY-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251031/202510311331.IAWNYwBY-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/oe-kbuild-all/202510311331.IAWNYwBY-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/nstree.c:7:28: sparse: sparse: symbol 'ns_tree_lock' was not declared. Should it be static?
kernel/nstree.c: note: in included file (through include/linux/ns_common.h, include/linux/nstree.h):
include/linux/rbtree.h:74:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/rbtree.h:74:9: sparse: struct rb_node [noderef] __rcu *
include/linux/rbtree.h:74:9: sparse: struct rb_node *
include/linux/rbtree.h:74:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/rbtree.h:74:9: sparse: struct rb_node [noderef] __rcu *
include/linux/rbtree.h:74:9: sparse: struct rb_node *
vim +/ns_tree_lock +7 kernel/nstree.c
6
> 7 __cacheline_aligned_in_smp DEFINE_SEQLOCK(ns_tree_lock);
8 static struct rb_root ns_unified_tree = RB_ROOT; /* protected by ns_tree_lock */
9
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-31 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202510311331.IAWNYwBY-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=oe-kbuild-all@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.