[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <xeipv5m2xxjfyhoqifdigymobmo5lnh6kqqloowbg4oiejqyp4@ns5iehb3kzof>
Date: Fri, 16 Jan 2026 15:19:30 -0500
From: "Liam R. Howlett" <Liam.Howlett@...cle.com>
To: kernel test robot <lkp@...el.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, oe-kbuild-all@...ts.linux.dev,
Linux Memory Management List <linux-mm@...ck.org>,
maple-tree@...ts.infradead.org, linux-kernel@...r.kernel.org,
Suren Baghdasaryan <surenb@...gle.com>,
Matthew Wilcox <willy@...radead.org>,
Sidhartha Kumar <sidhartha.kumar@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, Alice Ryhl <aliceryhl@...gle.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Arnd Bergmann <arnd@...db.de>, Christian Kujau <lists@...dbynature.de>
Subject: Re: [PATCH 16/28] maple_tree: Start using maple copy node for
destination
* kernel test robot <lkp@...el.com> [260116 04:37]:
> Hi Liam,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on akpm-mm/mm-everything]
> [also build test WARNING on next-20260115]
> [cannot apply to akpm-mm/mm-nonmm-unstable soc/for-next linus/master v6.19-rc5]
> [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#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Liam-R-Howlett/maple_tree-Move-mas_spanning_rebalance-loop-to-function/20260116-034135
> base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> patch link: https://lore.kernel.org/r/20260115193647.1695937-17-Liam.Howlett%40oracle.com
> patch subject: [PATCH 16/28] maple_tree: Start using maple copy node for destination
> config: x86_64-randconfig-121-20260116 (https://download.01.org/0day-ci/archive/20260116/202601161750.eDtUQiJr-lkp@intel.com/config)
> compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260116/202601161750.eDtUQiJr-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@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202601161750.eDtUQiJr-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> lib/maple_tree.c:3355:37: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got struct maple_enode * @@
> lib/maple_tree.c:3355:37: sparse: expected void [noderef] __rcu *
> lib/maple_tree.c:3355:37: sparse: got struct maple_enode *
> >> lib/maple_tree.c:3358:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct maple_enode const *entry @@ got void [noderef] __rcu * @@
> lib/maple_tree.c:3358:17: sparse: expected struct maple_enode const *entry
> lib/maple_tree.c:3358:17: sparse: got void [noderef] __rcu *
> >> lib/maple_tree.c:3397:19: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct maple_enode *node @@ got void [noderef] __rcu * @@
> lib/maple_tree.c:3397:19: sparse: expected struct maple_enode *node
> lib/maple_tree.c:3397:19: sparse: got void [noderef] __rcu *
> lib/maple_tree.c:3139:29: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got struct maple_enode * @@
> lib/maple_tree.c:3139:29: sparse: expected void [noderef] __rcu *
> lib/maple_tree.c:3139:29: sparse: got struct maple_enode *
> >> lib/maple_tree.c:2558:52: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct maple_enode *enode @@ got void [noderef] __rcu * @@
> lib/maple_tree.c:2558:52: sparse: expected struct maple_enode *enode
> lib/maple_tree.c:2558:52: sparse: got void [noderef] __rcu *
> lib/maple_tree.c:2803:29: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got void *content @@
> lib/maple_tree.c:2803:29: sparse: expected void [noderef] __rcu *
> lib/maple_tree.c:2803:29: sparse: got void *content
> lib/maple_tree.c:2806:23: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got void *entry @@
> lib/maple_tree.c:2806:23: sparse: expected void [noderef] __rcu *
> lib/maple_tree.c:2806:23: sparse: got void *entry
> >> lib/maple_tree.c:2558:52: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct maple_enode *enode @@ got void [noderef] __rcu * @@
> lib/maple_tree.c:2558:52: sparse: expected struct maple_enode *enode
> lib/maple_tree.c:2558:52: sparse: got void [noderef] __rcu *
> lib/maple_tree.c:6899:30: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got struct maple_node * @@
> lib/maple_tree.c:6899:30: sparse: expected void [noderef] __rcu *
> lib/maple_tree.c:6899:30: sparse: got struct maple_node *
> lib/maple_tree.c:6899:30: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __rcu * @@ got struct maple_node * @@
> lib/maple_tree.c:6899:30: sparse: expected void [noderef] __rcu *
> lib/maple_tree.c:6899:30: sparse: got struct maple_node *
>
...
Andrew,
Fixing these in patch 16 means that future patches will need fixing.
I can either send you patches to fix up this and subsequent patches. It
might be better for me to respin the series?
Let me know what you think I should do here.
I'll also include a final patch to correct any other sparse warnings.
Thanks,
Liam
Powered by blists - more mailing lists