linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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 418/422] fs/orangefs/file.c:414:9: sparse: sparse: dereference of noderef expression
Date: Tue, 20 Jan 2026 17:10:47 +0800	[thread overview]
Message-ID: <202601201701.IhxeGffs-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:   e4348a62bb1acacafcdeb149c9363291fae08c0c
commit: ccbdd8044f13617fe9f2bce61aed556314544664 [418/422] mm: update all remaining mmap_prepare users to use vma_flags_t
config: arm-randconfig-r131-20260120 (https://download.01.org/0day-ci/archive/20260120/202601201701.IhxeGffs-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260120/202601201701.IhxeGffs-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/202601201701.IhxeGffs-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/orangefs/file.c:414:9: sparse: sparse: dereference of noderef expression
   fs/orangefs/file.c: note: in included file (through arch/arm/include/asm/cacheflush.h, include/linux/cacheflush.h, include/linux/highmem.h, ...):
   include/linux/mm.h:1048:16: sparse: sparse: dereference of noderef expression
   include/linux/mm.h:1048:16: sparse: sparse: dereference of noderef expression
   include/linux/mm.h:1199:46: sparse: sparse: dereference of noderef expression
   include/linux/mm.h:1199:46: sparse: sparse: dereference of noderef expression
   fs/orangefs/file.c:415:9: sparse: sparse: dereference of noderef expression
   include/linux/mm.h:1048:16: sparse: sparse: dereference of noderef expression
   include/linux/mm.h:1048:16: sparse: sparse: dereference of noderef expression
   include/linux/mm.h:1216:48: sparse: sparse: dereference of noderef expression
   include/linux/mm.h:1216:48: sparse: sparse: dereference of noderef expression
--
>> fs/ramfs/file-nommu.c:267:40: sparse: sparse: dereference of noderef expression
>> fs/ramfs/file-nommu.c:267:40: sparse: sparse: dereference of noderef expression
   fs/ramfs/file-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 +414 fs/orangefs/file.c

   397	
   398	/*
   399	 * Memory map a region of a file.
   400	 */
   401	static int orangefs_file_mmap_prepare(struct vm_area_desc *desc)
   402	{
   403		struct file *file = desc->file;
   404		int ret;
   405	
   406		ret = orangefs_revalidate_mapping(file_inode(file));
   407		if (ret)
   408			return ret;
   409	
   410		gossip_debug(GOSSIP_FILE_DEBUG,
   411			     "orangefs_file_mmap: called on %pD\n", file);
   412	
   413		/* set the sequential readahead hint */
 > 414		vma_desc_set_flags(desc, VMA_SEQ_READ_BIT);
   415		vma_desc_clear_flags(desc, VMA_RAND_READ_BIT);
   416	
   417		file_accessed(file);
   418		desc->vm_ops = &orangefs_file_vm_ops;
   419		return 0;
   420	}
   421	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2026-01-20  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  9:10 kernel test robot [this message]
2026-01-20 10:56 ` Lorenzo Stoakes
2026-01-20 12:11   ` 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=202601201701.IhxeGffs-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