From: kernel test robot <lkp@intel.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev, Vlastimil Babka <vbabka@suse.cz>
Subject: [vbabka:maple-tree-sheaves-v3-hack 19/21] lib/maple_tree.c:6481:30: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Mon, 10 Feb 2025 20:53:00 +0800 [thread overview]
Message-ID: <202502102217.0YW7bpVS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/linux.git maple-tree-sheaves-v3-hack
head: 9b7a825f40a76d8502c0e96c19cfd47c53d8bd4d
commit: 0cf12ebfec24f08ea972ca4a28b71f0b212388e0 [19/21] maple_tree: Convert forking to use the sheaf interface
config: hexagon-randconfig-r113-20250210 (https://download.01.org/0day-ci/archive/20250210/202502102217.0YW7bpVS-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce: (https://download.01.org/0day-ci/archive/20250210/202502102217.0YW7bpVS-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/202502102217.0YW7bpVS-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/maple_tree.c:6481:30: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got struct maple_node * @@
lib/maple_tree.c:6481:30: sparse: expected void [noderef] __rcu *
lib/maple_tree.c:6481:30: sparse: got struct maple_node *
>> lib/maple_tree.c:6481:30: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got struct maple_node * @@
lib/maple_tree.c:6481:30: sparse: expected void [noderef] __rcu *
lib/maple_tree.c:6481:30: sparse: got struct maple_node *
vim +6481 lib/maple_tree.c
6448
6449 /*
6450 * mas_dup_alloc() - Allocate child nodes for a maple node.
6451 * @mas: The maple state of source tree.
6452 * @new_mas: The maple state of new tree.
6453 * @gfp: The GFP_FLAGS to use for allocations.
6454 *
6455 * This function allocates child nodes for @new_mas->node during the duplication
6456 * process. If memory allocation fails, @mas is set to -ENOMEM.
6457 */
6458 static inline void mas_dup_alloc(struct ma_state *mas, struct ma_state *new_mas,
6459 gfp_t gfp)
6460 {
6461 struct maple_node *node = mte_to_node(mas->node);
6462 struct maple_node *new_node = mte_to_node(new_mas->node);
6463 enum maple_type type;
6464 unsigned char count, i;
6465 void __rcu **slots;
6466 void __rcu **new_slots;
6467 unsigned long val;
6468
6469 /* Allocate memory for child nodes. */
6470 type = mte_node_type(mas->node);
6471 new_slots = ma_slots(new_node, type);
6472 count = mas->node_request = mas_data_end(mas) + 1;
6473 mas_alloc_nodes(mas, gfp);
6474 if (unlikely(mas_is_err(mas)))
6475 return;
6476
6477 slots = ma_slots(node, type);
6478 for (i = 0; i < count; i++) {
6479 val = (unsigned long)mt_slot_locked(mas->tree, slots, i);
6480 val &= MAPLE_NODE_MASK;
> 6481 new_slots[i] = ma_mnode_ptr((unsigned long)mas_pop_node(mas) |
6482 val);
6483 }
6484 }
6485
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-10 12:53 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=202502102217.0YW7bpVS-lkp@intel.com \
--to=lkp@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vbabka@suse.cz \
/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.