From: kernel test robot <lkp@intel.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.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 420/429] fs/romfs/mmap-nommu.c:66:42: sparse: sparse: dereference of noderef expression
Date: Thu, 22 Jan 2026 16:04:37 +0800 [thread overview]
Message-ID: <202601221505.RxftadLx-lkp@intel.com> (raw)
Hi Lorenzo,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: dc4fe40a11269aead253fa0beb098b00417b8694
commit: 57a654376d4bb67119d436edc8c3c4c0ecb3c369 [420/429] mm: update all remaining mmap_prepare users to use vma_flags_t
config: sh-randconfig-r122-20260122 (https://download.01.org/0day-ci/archive/20260122/202601221505.RxftadLx-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260122/202601221505.RxftadLx-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/202601221505.RxftadLx-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/romfs/mmap-nommu.c:66:42: sparse: sparse: dereference of noderef expression
>> fs/romfs/mmap-nommu.c:66:42: sparse: sparse: dereference of noderef expression
fs/romfs/mmap-nommu.c: note: in included file:
include/linux/mm.h:1954:16: sparse: sparse: dereference of noderef expression
include/linux/mm.h:1954:16: sparse: sparse: dereference of noderef expression
include/linux/mm.h:1048:16: sparse: sparse: dereference of noderef expression
include/linux/mm.h:1954:16: sparse: sparse: dereference of noderef expression
include/linux/mm.h:1048:16: sparse: sparse: dereference of noderef expression
vim +66 fs/romfs/mmap-nommu.c
59
60 /*
61 * permit a R/O mapping to be made directly through onto an MTD device if
62 * possible
63 */
64 static int romfs_mmap_prepare(struct vm_area_desc *desc)
65 {
> 66 return is_nommu_shared_vma_flags(desc->vma_flags) ? 0 : -ENOSYS;
67 }
68
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-22 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 8:04 kernel test robot [this message]
2026-01-22 21:23 ` Andrew Morton
2026-01-23 4:19 ` Philip Li
2026-01-23 5:48 ` Andrew Morton
2026-01-23 12:36 ` Lorenzo Stoakes
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=202601221505.RxftadLx-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox