From: kernel test robot <lkp@intel.com>
To: Muchun Song <songmuchun@bytedance.com>
Cc: oe-kbuild-all@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-new 159/160] include/linux/mmzone.h:2052:18: sparse: sparse: incorrect type in return expression (different address spaces)
Date: Wed, 15 Apr 2026 21:31:13 +0800 [thread overview]
Message-ID: <202604152138.zbTaYxbG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: f358e95febcb2f3d7ac6aafab0a2b9ace9cc8b7c
commit: 085038a33b6f00e4c43cceab8116315d1d42380c [159/160] mm/sparse: fix race on mem_section->usage in pfn walkers
config: i386-randconfig-r132-20260415 (https://download.01.org/0day-ci/archive/20260415/202604152138.zbTaYxbG-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260415/202604152138.zbTaYxbG-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/202604152138.zbTaYxbG-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
mm/sparse.c: note: in included file:
>> mm/internal.h:987:19: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct mem_section_usage [noderef] __rcu *usage @@ got struct mem_section_usage *usage @@
mm/internal.h:987:19: sparse: expected struct mem_section_usage [noderef] __rcu *usage
mm/internal.h:987:19: sparse: got struct mem_section_usage *usage
--
mm/page_alloc.c: note: in included file (through include/linux/gfp.h, include/linux/mm.h):
>> include/linux/mmzone.h:2052:18: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected unsigned long * @@ got unsigned long [noderef] __rcu * @@
include/linux/mmzone.h:2052:18: sparse: expected unsigned long *
include/linux/mmzone.h:2052:18: sparse: got unsigned long [noderef] __rcu *
>> include/linux/mmzone.h:2052:18: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected unsigned long * @@ got unsigned long [noderef] __rcu * @@
include/linux/mmzone.h:2052:18: sparse: expected unsigned long *
include/linux/mmzone.h:2052:18: sparse: got unsigned long [noderef] __rcu *
>> include/linux/mmzone.h:2052:18: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected unsigned long * @@ got unsigned long [noderef] __rcu * @@
include/linux/mmzone.h:2052:18: sparse: expected unsigned long *
include/linux/mmzone.h:2052:18: sparse: got unsigned long [noderef] __rcu *
>> include/linux/mmzone.h:2052:18: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected unsigned long * @@ got unsigned long [noderef] __rcu * @@
include/linux/mmzone.h:2052:18: sparse: expected unsigned long *
include/linux/mmzone.h:2052:18: sparse: got unsigned long [noderef] __rcu *
>> include/linux/mmzone.h:2052:18: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected unsigned long * @@ got unsigned long [noderef] __rcu * @@
include/linux/mmzone.h:2052:18: sparse: expected unsigned long *
include/linux/mmzone.h:2052:18: sparse: got unsigned long [noderef] __rcu *
vim +2052 include/linux/mmzone.h
d41dee369bff3b Andy Whitcroft 2005-06-23 2049
f1eca35a0dc7cb Dan Williams 2019-07-18 2050 static inline unsigned long *section_to_usemap(struct mem_section *ms)
f1eca35a0dc7cb Dan Williams 2019-07-18 2051 {
f1eca35a0dc7cb Dan Williams 2019-07-18 @2052 return ms->usage->pageblock_flags;
f1eca35a0dc7cb Dan Williams 2019-07-18 2053 }
f1eca35a0dc7cb Dan Williams 2019-07-18 2054
:::::: The code at line 2052 was first introduced by commit
:::::: f1eca35a0dc7cb3cdb00c88c8c5e5138a65face0 mm/sparsemem: introduce struct mem_section_usage
:::::: TO: Dan Williams <dan.j.williams@intel.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-15 13:32 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=202604152138.zbTaYxbG-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=songmuchun@bytedance.com \
/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.