From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: include/linux/rbtree.h:74:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
Date: Mon, 15 Dec 2025 00:44:31 +0800 [thread overview]
Message-ID: <202512150042.fpiqhcnF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
commit: 885fc8ac0a4dc70f5d87b80b0977292870e35c60 nstree: make iterator generic
date: 3 months ago
config: m68k-randconfig-r133-20251214 (https://download.01.org/0day-ci/archive/20251215/202512150042.fpiqhcnF-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251215/202512150042.fpiqhcnF-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/202512150042.fpiqhcnF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
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 *
vim +74 include/linux/rbtree.h
^1da177e4c3f41 Linus Torvalds 2005-04-16 67
d72da4a4d973d8 Peter Zijlstra 2015-05-27 68 static inline void rb_link_node_rcu(struct rb_node *node, struct rb_node *parent,
d72da4a4d973d8 Peter Zijlstra 2015-05-27 69 struct rb_node **rb_link)
d72da4a4d973d8 Peter Zijlstra 2015-05-27 70 {
d72da4a4d973d8 Peter Zijlstra 2015-05-27 71 node->__rb_parent_color = (unsigned long)parent;
d72da4a4d973d8 Peter Zijlstra 2015-05-27 72 node->rb_left = node->rb_right = NULL;
d72da4a4d973d8 Peter Zijlstra 2015-05-27 73
d72da4a4d973d8 Peter Zijlstra 2015-05-27 @74 rcu_assign_pointer(*rb_link, node);
d72da4a4d973d8 Peter Zijlstra 2015-05-27 75 }
d72da4a4d973d8 Peter Zijlstra 2015-05-27 76
:::::: The code at line 74 was first introduced by commit
:::::: d72da4a4d973d8a0a0d3c97e7cdebf287fbe3a99 rbtree: Make lockless searches non-fatal
:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Rusty Russell <rusty@rustcorp.com.au>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-14 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 16:44 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-29 16:45 include/linux/rbtree.h:74:9: sparse: sparse: incompatible types in comparison expression (different address spaces): kernel test robot
2025-05-20 9:31 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=202512150042.fpiqhcnF-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox